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

With no annotations, the description carries the full burden of behavioral disclosure. It only says 'Key discarded,' which is unclear and does not explain side effects, safety, read-only nature, or what the tool does with the input beyond a vague discard note. No information about permissions, reversibility, or output is given.

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, but it is under-specified rather than concise. It does not earn its place because it omits essential information about which parameter to use and what the check entails. The one-sentence format is not a virtue when it leaves critical gaps.

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 optional parameters, no annotations, and no output schema, the description is completely inadequate. It fails to specify the input parameter, the expected format of a Jira key, the return value, or any usage context. 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 the baseline is 3, but the description adds no value in mapping parameters. It never states which parameter holds the Jira key; schema descriptions mention 'Git ref name,' 'URL,' etc., none of which clearly align with a Jira key. The description fails to compensate for the ambiguity and may even mislead by not clarifying the intended 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 states the action (check) and resource (Jira issue key shape), so it is not a tautology. However, it is vague about which of the nine parameters holds the key and does not differentiate from sibling shape-checking tools like github-repo-shape or figma-url-shape. The phrase 'Key discarded' hints at behavior but not the input.

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 on when to use this tool versus the many sibling shape-checkers (domain-shape, figma-url-shape, github-repo-shape, etc.). No conditions, exclusions, or alternative tools are mentioned, leaving the agent without any selection criteria.

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