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

No annotations are provided, so the description carries the full burden. It only states 'No identifiers are retained,' which addresses data retention but reveals nothing about side effects, return format, or whether the tool is read-only. The operational behavior remains completely opaque.

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 (two sentences) but under-specifies the tool's purpose. It is not 'concisely informative' – it omits critical information, making it more an empty shell than a well-structured 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?

With 9 heterogeneous parameters, no output schema, and no annotations, the description is severely inadequate. An agent cannot determine what the tool does, what inputs are needed, or what output to expect, making it impossible to call 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 each parameter already has a clear description (e.g., 'Git ref name; discarded after the shape check'). The tool description adds no additional parameter meaning, so the baseline 3 is appropriate.

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 'Show how this request is classified' is extremely vague; it never specifies what 'classified' means, what kind of classification is performed, or what the tool actually does with the 9 input parameters. It fails to differentiate from many sibling tools that perform concrete checks (e.g., validate-json, browser-url-ok, domain-shape).

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?

The description offers no guidance on when to use this tool versus any of the 30 siblings. It mentions no conditions, alternatives, or exclusions, leaving the agent entirely without routing information.

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