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

The description says 'Key discarded' and some schema fields mention 'discarded after the check', implying no persistence, but it does not clarify side effects, return format, or whether any network/disk access occurs. With no annotations, this leaves important behavioral details undisclosed.

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 brief and free of fluff, which is good for conciseness, but it omits essential information about input expectations. It is structurally simple but not sufficiently informative for a usable tool description.

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 confusing schema and lack of output schema, the description is far from complete. It does not explain how to pass the Jira key, what a valid key looks like, whether the tool returns a boolean or error, or how it differs from the numerous sibling validation tools.

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?

The schema contains nine generic parameters (ref, url, city, feed, host, json, path, zone, query) with descriptions unrelated to a Jira key shape check. There is no parameter clearly designated as the Jira key, and the descriptions add no useful mapping to the tool's purpose. This is severely misleading.

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 the tool checks a Jira issue key shape, which conveys a general validation purpose, but it does not specify what constitutes a valid shape (e.g., 'PROJ-123') or what the tool returns. It is clearer than a pure tautology but leaves key semantics ambiguous.

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 sibling shape/length checkers like 'github-repo-shape', 'domain-shape', or 'search-query-len'. No conditions, examples, or alternative selection criteria are provided.

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