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

Without annotations, the description carries the transparency burden. 'Key discarded' discloses that the input is not retained and the operation is a pure check, but it does not explain the return value, failure behavior, or whether a network call is involved. Some transparency is present, but the full behavioral contract is missing.

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 redundant wording. The action is front-loaded, and 'Key discarded' adds a useful behavioral note without extra fluff.

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 no output schema and no annotations, the description should at least identify the parameter to pass and what result to expect. It does neither, and the large unrelated schema makes the invocation ambiguous. The simple intent is clear from the name, but the operational details needed to call the tool correctly are missing.

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 the schema has 100% description coverage, the description never connects 'the key' to any of the 9 schema properties. The schema lists ref, url, city, feed, host, json, path, and others, none of which is described as a Jira issue key, so an agent cannot confidently determine which parameter to populate. The 'Key discarded' phrase adds no parameter-level mapping.

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 uses a specific verb ('Check') and a specific resource ('Jira issue key shape'), and the name separates it from sibling shape-checkers like github-repo-shape and domain-shape. It stops short of a 5 because it does not specify what 'shape' means or what a valid result looks like, leaving some ambiguity.

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 choose this tool over siblings such as github-repo-shape, wiki-title-ok, or normalize-url. The intended use is only implied by the tool name and the phrase 'Jira issue key shape'; no exclusions or alternative conditions are stated.

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