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. The only behavioral hint is 'Key discarded,' which implies the input is not stored or persisted, but it does not state the return value (e.g., a boolean, a normalized key, or an error), whether any side effects occur, or whether network access is involved. For a validation tool, this is severely incomplete.

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 short (two sentences) but it is under-specified rather than appropriately concise. It fails to convey essential information about the tool's operation or parameters. While brevity is generally positive, here it sacrifices clarity and completeness, so it does not earn a high conciseness 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?

For a tool with 9 optional parameters, no output schema, and no annotations, the description is grossly inadequate. It does not explain the purpose clearly, does not identify which parameter is the Jira key, does not describe the output or behavior, and does not relate to sibling tools. An agent cannot reliably decide to use this tool or know how 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% with each parameter having a terse description (e.g., 'Git ref name; discarded after the shape check'), so the baseline is 3. However, the tool description references a 'Jira issue key' while none of the schema parameters are labeled as such, and the descriptions do not clarify which field to use for the key. The description adds no meaning beyond the schema and actually creates ambiguity about which parameter is relevant. Thus the score drops to 2.

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 specific verb ('check') and resource ('Jira issue key shape'), but it is vague about what 'shape' means (format validation?) and, critically, does not indicate which of the nine schema parameters holds the Jira key. None of the parameter names or schema descriptions mention 'Jira' or 'key', so the agent cannot map the description to the input. It also does not distinguish itself from sibling tools like github-repo-shape or domain-shape beyond the noun 'Jira'.

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 zero guidance on when to use this tool versus the many sibling shape-checking tools (domain-shape, figma-url-shape, github-repo-shape, etc.). No context is given about which input types are appropriate or what distinguishes a Jira key from other identifiers. The description provides no usage conditions or alternatives.

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