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

The only behavioral disclosure is 'Key discarded,' which indicates the input is not retained. No annotations are present, so the description carries full burden, but it does not mention return values, side effects on other parameters, or whether the tool validates only Jira keys or also handles the other schema fields. The mismatch between description and schema is undisclosed.

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 only two sentences, but it is under-specified rather than concise. It omits essential information about scope, behavior, and relationship to the schema, so the brevity does not serve efficiency.

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?

For a tool with 9 parameters, no output schema, and no annotations, the description is severely inadequate. It explains neither what the tool returns, how it handles each parameter, nor how the Jira key concept connects to the diverse schema fields. An agent cannot correctly invoke this tool based on the description alone.

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?

Schema coverage is 100%, so baseline is 3, but the description adds zero parameter information and actually conflicts with the schema. The schema lists parameters like city, json, path, and zone, while the description implies only a Jira key is checked. This mismatch misleads the agent about which parameter is relevant, so the description fails to add meaning and even undermines clarity.

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 states a specific verb and resource: 'Check a Jira issue key shape.' This distinguishes it from sibling shape tools by name. However, it lacks detail on what 'shape' means (e.g., pattern, format) and does not mention how the tool relates to the many unrelated parameters in the schema, which confuses the actual purpose.

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?

No guidance is given on when to use this tool versus other shape-checking siblings like 'domain-shape' or 'github-repo-shape'. The description does not state prerequisites, typical use cases, or when to prefer an alternative.

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