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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Key discarded' hints that the input is not persisted, but it does not disclose whether the tool returns a boolean, validates strictly, or has any side effects. This is insufficient for a validation tool with no output schema.

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 short and front-loaded, with no wasted words. However, it is so terse that it omits critical information, and the phrase 'Key discarded' is ambiguous about the tool's behavior and input requirements.

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 annotations, no output schema, and a nine-parameter schema that does not contain the described 'key', the description is fundamentally incomplete. An agent cannot safely select or invoke this tool without guessing the intended parameter mapping and expected return value.

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 description mentions a 'Key', but the input schema has no 'key' property; instead it exposes nine unrelated properties such as url, city, feed, host, json, path, zone, and query. Even though the schema descriptions cover those nine parameters at 100%, none maps to a Jira issue key, so an agent cannot determine what to pass to this tool.

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 clearly states a specific action ('Check') on a specific resource ('a Jira issue key shape'), which distinguishes it from sibling shape tools like domain-shape or github-repo-shape. However, it does not define what 'shape' means or explain the result format, so it is clear but not fully self-sufficient.

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 about when to use this tool versus alternatives. The description gives only a bare imperative and no context, exclusions, or mention of related tools such as domain-shape or github-repo-shape.

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