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

The description notes the input is discarded, which is a minimal behavioral disclosure. With no annotations provided, it fails to state what happens on success/failure, whether external access occurs, or any side effects, leaving the agent guessing about the tool's 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 description is extremely concise (two short sentences), which is structurally clean, but it omits critical information needed to use the tool. It is under-specified rather than appropriately brief, so the conciseness is counterproductive.

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 9 optional parameters and no output schema, the description provides almost no contextual guidance. It does not identify the key parameter, explain return values, or indicate how to construct a valid call, making it grossly inadequate for correct invocation.

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 descriptions cover all 9 parameters, but none of them reference a Jira key. The main description adds no mapping between the stated purpose and the actual parameters, so an agent cannot infer which parameter to pass or how the parameters relate to the key shape check.

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 clear purpose: checking the shape of a Jira issue key. However, it does not indicate which of the 9 schema parameters carries the Jira key, making the purpose ambiguous in practice. It also fails to differentiate from sibling shape-checkers like 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?

No guidance on when to use this tool versus alternatives. The phrase 'Key discarded' hints at a non-persistent check, but does not specify conditions for use or exclusions relative to sibling shape tools.

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