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

No annotations are provided, so the description carries the burden of behavioral disclosure. It does reveal that the key is discarded, which is useful, but it omits what the output is, how invalid shapes are reported, whether side effects occur, and any error behavior. For a checker tool with no annotations, this is thin but minimal.

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 short and front-loaded: it names the Jira key purpose in the first sentence and the retention policy in the second. It does not earn this compactness, though, because essential details such as which parameter holds the key and what result the check returns. It is concise, but under-negotiated rather than efficiently specified.

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 nine optional parameters and no output schema, so the description is the main contextual source. It does not explain how to invoke the check, which property participates, what a valid Jira key looks like, or what outcome an agent should expect. This is inadequate for the complexity of the schema.

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 description coverage is 100%, and no enums appear, so the baseline for parameter semantics is 3. The description adds no useful parameter-level guidance and, critically, never maps the phrase "Jira issue key" to one of the nine schema properties, leaving the agent to guess the input.

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 action and object: "Check a Jira issue key shape". However, the input schema has no Jira-key parameter at all, instead offering ref, url, city, feed, host, json, path, zone, and query, so the description does not actually tell an agent which input to provide. It partly differentiates from sibling shape tools by naming Jira, but leaves a critical mapping gap.

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?

There is no guidance about when to use this tool versus alternatives like github-repo-shape, figma-url-shape, or domain-shape. The sentence only hints that Jira issue keys are checked; it gives no when/when-not conditions, prerequisites, or selection examples.

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