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

With no annotations provided, the description carries the behavioral burden. 'Key discarded' adds some transparency by implying no retention or side effects, but it does not describe the return value or behavior for invalid shapes. This is minimal but not misleading.

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 short and front-loaded, with each sentence serving a purpose: stating the action and noting the input is discarded. It is concise, though the terse style contributes to the missing parameter linkage.

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 no annotations and no output schema, the description is under-specified for a tool with seven parameters. It does not explain what constitutes a valid Jira key shape, which parameter to supply, or what the tool returns. An agent would struggle to invoke it correctly.

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 every schema property has a description and coverage is high, the critical ambiguity remains: none of the seven parameters is explicitly identified as the Jira key input. The description mentions 'Key discarded' but does not link it to a specific field such as ref, url, or path, so an agent cannot confidently select the right parameter.

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 resource and action: 'Check a Jira issue key shape.' This distinguishes it from sibling shape tools like domain-shape or figma-url-shape. However, it does not specify which input parameter carries the key, 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?

No guidance is given about when to use this tool versus alternatives such as github-repo-shape or file-path-ok. There are no explicit conditions, exclusions, or references to sibling tools, so the agent must rely solely on the tool name.

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