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

With no annotations provided, the description carries the full behavioral disclosure burden. It does say the 'Key discarded,' which is a useful non-retention detail, but it does not disclose whether the operation is read-only, what it returns, whether any network call is made, or what side effects could occur.

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 very concise: two short sentences with the core action front-loaded. The second sentence 'Key discarded' adds some behavioral context but is cryptic, so it is not fully self-explanatory despite being lean.

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 has no output schema, no annotations, nine optional parameters, and no explicit indication of which parameter is required for the check. The description does not explain return values, validation criteria, or how to supply the key, making it incomplete for reliable invocation.

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?

Although schema coverage is 100%, the description mentions a 'key' but never maps it to any of the nine schema parameters; none of them is named 'key' or 'issue_key.' The schema parameters are generic strings like ref, url, host, and path, so an agent cannot confidently determine which parameter should hold the Jira key.

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 names the operation ('Check') and the resource ('a Jira issue key shape'), which distinguishes it from sibling shape-checkers like domain-shape or figma-url-shape. However, it does not define what 'shape' means or what a valid key looks like, leaving some 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 gives no explicit when-to-use guidance, no alternative tool references, and no exclusions. An agent must infer entirely from the name and the one-line description, which is minimal compared to the large sibling set of similar validators.

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