List classifications

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

The annotation readOnlyHint=true already tells the agent this is a safe read operation. The description adds little: it mentions 'catalog required by Product.create', which could hint at a required filter context, but it doesn't clarify what the tool actually does or what happens when used without a catalog. There is no contradiction, but the behavioral context is minimal and confusing.

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 only one sentence, which is brief, but it's not effectively concise because the sentence is opaque and fails to communicate the tool's purpose. It reads more like a developer note than a user-facing description, making it under-specified rather than efficient.

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 simple list tool with read-only annotation and two documented params, the description should quickly clarify what classifications are, why 'catalog' matters, and how this fits with Product.create. Instead, it leaves these questions unanswered, so the tool's context is incomplete despite the rich schema and sibling context.

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 full descriptions for both parameters (limit and query), so the schema alone is sufficient. The description does not add any parameter-level information beyond what's in the schema. Baseline of 3 is appropriate since coverage is 100% and the description doesn't mislead about parameters.

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 title and name clearly say 'List classifications', but the description itself is cryptic: 'Classification.filter: catalog required by Product.create.' It doesn't explicitly state that the tool lists classifications or what the returned data represents. The phrase 'Classification.filter' suggests filtering, but the purpose is muddled and not clearly tied to the tool's function.

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 the many other list_* tools. The mention of 'catalog required by Product.create' implies a use case, but it's unclear whether the tool requires a catalog parameter (it does not have one) and how it relates to product creation. No comparison to alternatives or exclusions are provided.

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