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

The description discloses that the key is 'discarded,' implying no persistence or side effects, which is useful. But with no annotations provided, the description carries the full burden and fails to state what the check returns, whether it makes a network call, or how invalid shapes are handled. This is insufficient behavioral disclosure.

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 with no filler. It is front-loaded with the primary purpose. However, the brevity omits critical mapping details, so while structurally efficient, it sacrifices necessary information.

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 9-parameter tool with no annotations and no output schema, this description is severely incomplete. It fails to identify which parameter is the Jira key, does not describe the result format, and gives no error or edge-case behavior. An agent has almost no basis to invoke it correctly.

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 description coverage is 100%, so the baseline is 3, but the parameter descriptions are generic ('Git ref name', 'HTTPS URL', 'City name', etc.) and none of them clearly references a Jira issue key. The tool description mentions a key but gives no indication which parameter should receive it, making the parameter semantics misleading rather than clarifying.

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 action and resource: 'Check a Jira issue key shape.' This is clear at a high level and distinguishes the tool from sibling shape-checkers by name. However, it does not map the Jira key to any of the 9 input schema parameters, leaving the agent uncertain which field to populate.

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 versus alternatives like github-repo-shape, figma-url-shape, or domain-shape. The description only says what it does, not when an agent should select it over siblings or what conditions make it appropriate.

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