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

With no annotations, the description must disclose behavioral traits, but it only says 'Key discarded.' This implies inputs are not retained, but it does not explain what the tool actually returns, whether it is read-only, or how failures are signaled. It also fails to reconcile the 'Jira key' focus with the broad set of parameters, leaving the agent unsure of side effects or outcomes.

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 only two sentences, so it is not bloated. However, it is under-specified for a tool with 9 parameters and no output schema. Key information like return value, usage context, and the relationship between the name and the schema is absent. It is concise but not effectively structured to aid agent decision-making.

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 the complexity (9 parameters, no output schema, no annotations), the description is grossly incomplete. It does not explain what the tool checks beyond 'Jira key shape', nor does it clarify how the many parameters are used or what the result looks like. An agent cannot confidently call this tool based on the description alone.

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 description coverage is 100%, so each parameter already has a textual description (e.g., 'Git ref name; discarded after the shape check'). The tool description itself adds no extra parameter semantics, but since the schema carries the full burden, a baseline of 3 is appropriate. No additional value is provided.

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 verb+resource ('Check a Jira issue key shape'), so the core intent is clear. However, the input schema includes parameters like city, feed, host, json, and path that have nothing to do with Jira keys, suggesting the tool is actually a general-purpose shape checker. This mismatch confuses the purpose, and the description does not differentiate it from sibling shape tools such as domain-shape or github-repo-shape.

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 on when to use this tool versus alternatives. The description neither states the conditions under which it should be invoked nor mentions any exclusions. An agent cannot decide between this and the many other shape-checking tools without inspecting each sibling's schema.

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