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

The description discloses that the key is 'discarded' after checking, which implies no persistence or side effects. However, it does not state whether the tool performs any validation, returns a boolean, or throws errors. With no annotations, the agent has limited insight into the actual behavior beyond the simple check.

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 concise at just two sentences, but it omits essential details about the expected input format and output. It is well-structured but lacks the content needed to be truly effective, so it earns a middle score.

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 no output schema and no annotations, the description is the sole source of context. It fails to explain what the tool returns, how to interpret the result, or why the parameters are structured as they are. The vague and irrelevant parameter descriptions further reduce completeness, making it insufficient for an agent to use confidently.

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 the schema covers 100% of parameters, the descriptions are generic and unrelated to Jira keys. Parameter names like 'ref', 'url', 'city', 'feed', 'json', etc., with descriptions such as 'Git ref name' or 'City name for a public weather hint', are clearly mismatched with the tool's purpose. This is misleading and provides no meaningful semantics for the tool's actual 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 'Check a Jira issue key shape' states a clear action, but it does not specify what constitutes a valid Jira key shape (e.g., project key format, numeric ID) or what the tool returns. It is not distinguished from sibling shape-checking tools like 'domain-shape' or 'github-repo-shape', so an agent may not know when this is the right choice.

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 explicit guidance on when to use this tool versus alternatives. The description does not mention any conditions, prerequisites, or comparisons with sibling tools that check other kinds of shapes, leaving the agent to infer applicability.

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