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

With no annotations, the description carries the full burden for behavioral disclosure. 'Key discarded' is a useful disclosure that the input is not retained, but the description does not say whether the check is syntactic only, what happens on invalid shapes, or whether a network call is involved.

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 two short sentences with no wasted words, and the main action is front-loaded. 'Key discarded' is an efficient additional behavioral note.

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 nine parameters, no annotations, and no output schema, the description is radically incomplete. It does not identify the required parameter, describe the expected return value, or explain edge cases, so an agent cannot reliably invoke it.

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 each parameter has a description, but those descriptions describe unrelated concepts such as Git refs, URLs, timezone names, and search text. The description adds no parameter meaning, and critically, none of the parameters is identified as the Jira issue key, leaving the agent unable to select the correct 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 operation, checking a Jira issue key shape, and the 'Key discarded' note adds a privacy-relevant detail. However, the input schema exposes nine generic string parameters with no field that obviously holds a Jira key, so the stated purpose cannot be mapped to any input. This mismatch makes the purpose misleading rather than helpful.

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 sibling shape-checkers like github-repo-shape or domain-shape. The description implies it should be used for Jira issue keys, but it does not explain when not to use it or which alternative to prefer.

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