jira_add_label

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries full burden for behavioral disclosure. While it mentions the tool's purpose, it doesn't disclose important behavioral traits such as whether this requires specific permissions, if labels are case-sensitive, what happens when adding duplicate labels, or any rate limits. For a mutation tool with zero annotation coverage, this leaves significant gaps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is perfectly concise with two sentences that each earn their place: the first states the core functionality, and the second provides usage context. There's zero waste or redundancy, making it easy to parse and understand quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given this is a mutation tool with no annotations and no output schema, the description should do more to compensate. While it clearly states the purpose, it lacks information about behavioral constraints, error conditions, or what the tool returns. The 100% schema coverage helps with parameters, but overall completeness is only adequate for this complexity level.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema description coverage is 100%, with both parameters (issue_key and label) well-documented in the schema itself. The description doesn't add any meaningful parameter semantics beyond what's already in the schema, so it earns the baseline score of 3 for adequate but not additive documentation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the specific action ('Add a label/tag') and target resource ('to a Jira work item'), distinguishing it from siblings like jira_remove_label (which removes labels) and jira_set_field (which sets arbitrary fields). It provides a concise purpose statement with no ambiguity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context for when to use this tool ('to categorize and organize work items for easier filtering and tracking'), which implicitly suggests it's for organizational purposes rather than status changes or commenting. However, it doesn't explicitly state when NOT to use it or name specific alternatives like jira_set_field for other modifications.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.