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 states 'No identifiers are retained' which is a privacy note, and several parameter descriptions mention 'discarded after the check,' implying a non-persistent, read-only operation. However, it doesn't explicitly state whether the tool makes network calls, accesses local resources, or has side effects, and it doesn't describe the output format. Partial disclosure only.

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 one short sentence, which is concise, but it's under-specified rather than efficient. It omits critical information about the tool's purpose and output, so the brevity is not an asset. There is no structural organization or front-loading of key details beyond a vague statement.

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?

This tool has 9 optional parameters spanning many domains (Git refs, URLs, cities, RSS, JSON, paths, timezones, queries), yet the description gives no indication of what classification means, what output to expect, or how the tool integrates with the sibling tools. With no output schema and no annotations, the description is severely incomplete for an agent to call this tool effectively.

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. The tool description adds no parameter-specific detail, but the schema itself provides rich descriptions for all 9 parameters (e.g., 'discarded after the shape check'). The description doesn't need to add more since the schema covers it, so the baseline holds.

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 says 'Show how this request is classified' which is a verb+resource but extremely vague. It doesn't clarify what 'classified' means, what compatibility refers to, or what distinguishes this from the many sibling tools that check specific inputs. It's not a tautology but gives little actionable meaning.

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 any of its 29 siblings. The description provides no context about what kind of request classification it performs or what inputs would make it the right choice. An agent has no basis to select it over alternatives.

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