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

No annotations are provided, so the description carries the transparency burden. It only says the key is discarded and some params say 'no disk access' or 'discarded', but it does not disclose read-only behavior, failure modes, or what happens with an invalid shape; the purpose-schema mismatch further hides actual behavior.

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 main description is very short and front-loaded ('Check a Jira issue key shape. Key discarded.'), with no fluff, but it is too terse to bridge the gap to the mismatched schema; the overall structure provides no helpful organization or examples.

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?

With nine parameters, no required fields, no output schema, and no annotations, an agent cannot determine which parameter holds the key, what input format is expected, or what result is returned; the tool is not complete enough for reliable use.

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 parameter has a schema description, the descriptions are incoherent with the tool purpose (e.g., 'Git ref name', 'City name for a public weather hint', 'JSON text to validate'); no parameter is clearly identified as the Jira key, so the descriptions add confusion rather than meaning.

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 tool checks a Jira issue key shape and discards the key, but the input schema exposes nine unrelated string parameters (ref, url, city, feed, host, json, path, zone, query) and no obvious key parameter, so an agent cannot map the stated purpose to an invocable 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 about when to use this tool instead of sibling shape/check tools such as domain-shape, github-repo-shape, figma-url-shape, or wiki-title-ok; no conditions, prerequisites, or examples are given.

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