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

The only disclosed behavior is 'Key discarded,' which signals non-retention but is the sole behavioral trait. With no annotations provided, the description carries the full burden and should also explain what the check does, whether it returns a boolean or normalized result, and whether it accesses any external resource; none of that is present.

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 very short, front-loads the main action, and contains no filler. Each sentence earns its place: the first identifies the intended operation, and the second adds a non-retention note. The brevity is clear, though it contributes to under-specification rather than being intentionally efficient.

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?

With seven heterogeneous input fields, no output schema, and no explanation of how those fields relate to a Jira issue key, the description is not complete enough for reliable invocation. It omits return values, parameter selection, error conditions, and any indication of which parameter actually carries the key.

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 all seven parameters have schema descriptions, they are generic disposal notes like 'discarded after the shape check' and none of them mentions a Jira issue key or connects the description's 'key' to a specific field. The description adds no mapping between the stated purpose and parameters such as ref, url, host, or json, so an agent cannot confidently choose the right input.

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 ('Check') and a specific resource ('a Jira issue key shape'), which distinguishes it from sibling shape tools like github-repo-shape or figma-url-shape. It does not define what 'shape' means or whether this is a regex-style validation, but the core purpose is recognizable.

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 instead of the many sibling shape/validation tools, nor any mention of prerequisites or context. The description merely states the function, leaving the agent to infer when a Jira key shape check should be invoked.

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