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

With no annotations, the description carries the full burden of behavioral disclosure, but it only says the key is discarded. It does not state whether validation is local, what output is returned, whether network access is involved, or what happens when the shape is invalid. This is a significant gap for a validation tool.

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 compact, front-loaded with the core action, and free of filler. Both sentences are relevant, though the brevity is caused by under-specification rather than by efficient completeness.

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 ten optional parameters, no annotations, and no output schema, the agent still lacks essential context: the return value, how to construct the Jira key input, and whether side effects or network calls occur. The description is not complete enough for reliable selection and invocation.

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 each parameter is already individually documented and the baseline is 3. The tool description adds no per-parameter meaning and fails to state which of the ten parameters should contain the Jira key; 'ref' is the closest hint because it is 'discarded after the shape check'. Since the description neither clarifies nor contradicts the schema, the baseline stands.

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 concrete action and resource ('Check a Jira issue key shape'), so it is not a tautology, but it never defines what constitutes a valid shape and the schema exposes no 'key' parameter. With ten heterogeneous optional parameters, an agent cannot confidently map the stated purpose to an invocation. It also does not distinguish this tool from sibling shape-check tools.

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 domain-shape, github-repo-shape, or figma-url-shape, nor any mention of the expected Jira key format such as 'PROJ-123'. The description leaves an agent to infer both the input source and the appropriate context, which is especially problematic given that no parameters are required.

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