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

There are no annotations to cover safety or side effects, so the description must carry the behavioral burden. It does state 'Key discarded,' which signals no retention, but it does not disclose what the tool returns, whether it succeeds/fails, or how it handles invalid shapes. This is insufficient for a check-style tool without an output schema.

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 extremely short and front-loaded with the main purpose. The second sentence carries the only behavioral detail without repeating the first. It is concise, but the terseness contributes to the ambiguity around which parameter to use.

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?

The tool is simple, but the schema is confusing and there is no output schema or annotations. The description does not explain return values, validation criteria, or which input field receives the Jira key. An agent would struggle to invoke this tool correctly despite knowing its high-level purpose.

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 has many string parameters with descriptions, but none correspond to a Jira issue key. The description mentions 'Key' but never maps it to any schema property. The presence of unrelated parameters like city, feed, json, and path makes it even harder for an agent to know what to pass. The description does not remedy this confusion at all.

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 clearly distinguishes it from sibling shape-check tools like github-repo-shape or domain-shape. The second sentence adds a side-effect note without confusing the core 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 usage context is provided. The description never says when to use this tool instead of alternatives, nor does it mention any exclusions or prerequisites. It only implies that this is for validating Jira issue keys, but provides no routing guidance.

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