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

The only behavioral disclosure is 'No identifiers are retained,' which is a privacy statement. Without annotations, the description must carry the full burden of disclosing side effects, output format, or constraints, but it says nothing about whether network calls occur, what the classification result looks like, or any other 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) and under-specifies for a tool with 9 mixed parameters. While concise, it lacks any structured information and is not front-loaded with key details because it has almost no content.

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 the tool has 9 heterogeneous parameters, no output schema, and no annotations, the description is severely inadequate. It does not explain what the output represents, how the parameters influence classification, or any usage constraints. An agent would be unable to use this tool 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 the input schema already thoroughly documents all 9 parameters. The description adds no parameter-specific meaning beyond that, matching the baseline of 3 for high coverage.

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' but does not specify what classification means, what types of requests are handled, or how the various parameters relate to classification. It is not a complete tautology, but it is vague and fails to differentiate from sibling shape-checking tools like domain-shape or figma-url-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?

No guidance is given on when to use this tool versus its siblings. It does not mention alternatives or conditions for selection. An agent cannot determine whether to call this generic classifier or a more specialized shape checker.

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