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

With no annotations, the description carries the transparency burden. It does disclose one behavioral trait: the key is discarded, suggesting the input is not retained. It does not explain whether the check is local, what it returns, or whether any side effects occur, so transparency is partial.

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 concise sentences with no filler or redundancy; the first states the action, the second adds a privacy-related behavior. It is appropriately front-loaded, though the second sentence is cryptic.

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?

This is a 9-parameter tool with no annotations and no output schema, yet the description omits the accepted key pattern, which parameter receives the key, return behavior, and error semantics. The description is inadequate for an agent to safely invoke the tool.

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?

The schema has 100% description coverage, but none of the nine parameters is named or described as a Jira issue key; properties reference Git refs, weather hints, RSS feeds, JSON, paths, and zone names. The description never tells the agent which parameter to populate, so the rich schema does not actually help in invoking this tool.

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 names a concrete action ('Check') and a specific resource ('Jira issue key shape'), so an agent can infer this is a validation tool for Jira issue keys. It does not explicitly contrast it with sibling shape-checkers like github-repo-shape or figma-url-shape, though the Jira resource itself is distinctive.

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 statement about when to choose this tool over the neighboring shape-validation tools, and no exclusion or alternative is mentioned. The action phrase only implies a use case; it does not say when-not-to-use.

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