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

With no annotations provided, the description must fully disclose behavior. It offers only a privacy note ('No identifiers are retained') but does not explain what the tool does, what it returns, or whether it makes network calls or performs validation. The schema parameter descriptions hint at checks and discarding, but the tool description itself is silent on its behavior.

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 short (one sentence), which is concise but under-specified. It lacks essential content about purpose and usage, so the brevity is not a strength; it is a deficiency.

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 parameters, no output schema, and no annotations, this description is woefully incomplete. It does not explain what 'classification' means, what the tool accepts, what it produces, or when to use it. An agent has almost no basis for correct 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?

The input schema provides 100% description coverage for all 9 parameters, each with a clear meaning (e.g., 'Git ref name; discarded after the shape check'). The description adds no group-level semantics or relationships between parameters, but since the schema already documents them, a baseline of 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 states a vague verb 'Show' and a resource 'how this request is classified', but 'classified' is ambiguous and does not specify the tool's actual function. It does not distinguish this tool from its many siblings (e.g., domain-shape, validate-json, normalize-url), leaving the agent unable to tell what unique capability it offers.

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. The description neither mentions scenarios for use nor contrasts with any sibling tools, so an agent cannot decide when this is the appropriate choice.

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