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

The description discloses one meaningful behavioral trait: the key is discarded, implying no retention. However, with no annotations provided, it does not state whether the tool makes network calls, requires auth, or what it returns (boolean, normalized key, error), leaving important behavioral gaps.

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 filler. The first sentence states the purpose and the second adds a distinct privacy-related behavior, so every word earns its place.

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?

Given nine optional parameters, no output schema, and no annotations, the description is not self-sufficient. It fails to identify the relevant input parameter, the expected output, or whether the operation is purely local, making it difficult for an agent to invoke the tool correctly.

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?

Even though the schema has 100% description coverage, the description references a 'key' that is not present among the nine schema properties, and it does not map the Jira key to any specific parameter. An agent cannot tell whether to pass 'ref', 'url', or some other field, so the description adds no useful parameter guidance.

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 clearly names the resource ('Jira issue key') and the action ('Check'), and the 'shape' wording signals format validation rather than API lookup. It also distinguishes this tool from sibling shape checkers like github-repo-shape or domain-shape, though it does not define what a valid Jira key shape is.

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?

The description gives no indication of when to use this tool over alternatives, nor does it mention any prerequisites or exclusions. With 26 sibling tools, an agent is left to infer the context from the name alone.

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