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

With no annotations at all, the description carries the full burden of behavioral disclosure. It only says 'Key discarded,' hinting that the input is not retained, but it does not state whether the tool returns a boolean, throws on invalid input, performs network calls, or has side effects. This is too thin for an unannotated tool.

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 compact sentences with no filler, and the core purpose is front-loaded. It is efficient, though extremely terse. The missing information is a completeness issue rather than a conciseness issue, so conciseness itself is good.

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 parameters, no annotations, and no output schema, this description is far from complete. It does not identify which parameter receives the Jira key, what result to expect, or what 'key discarded' means operationally. The tool is practically impossible to invoke correctly from the provided context.

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 schema coverage is 100%, the description adds no parameter meaning. More critically, the schema has nine string parameters, none of which is explicitly described as a Jira issue key. The only param mentioning 'shape check' is 'ref,' described as a 'Git ref name,' which is not the same as a Jira key. An agent cannot map 'Jira issue key' to any schema property with confidence.

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 action and resource: 'Check a Jira issue key shape.' This is more than a tautology because it adds a verb and a domain-specific object, and the appended 'Key discarded' gives a small behavioral clue. However, it does not distinguish among sibling shape-checking tools (e.g., github-repo-shape), so it stops short of full differentiation.

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 versus alternatives. The description gives no context, exclusions, or alternative tool suggestions. An agent would have to infer use cases from the name alone, which is insufficient for reliable tool selection.

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