get_classification

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

With no annotations provided, the description carries the full burden. It clearly indicates this is a lookup operation and states the ID precondition, but it does not disclose the response format, error behavior for invalid IDs, or any access constraints. This is adequate but not rich.

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?

Two sentences, front-loaded with the primary purpose and a practical usage hint. No wasted words, and the structure prioritizes the most actionable information.

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?

The tool has only 2 required parameters, no output schema, and a simple lookup purpose. The description covers what the tool does and how to acquire the required ID, which is sufficient for basic invocation. It lacks return value details, but the simplicity of the tool lessens the need for more.

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%; both parameters have detailed descriptions with examples and enum values. The description adds a reference to 'ID' but does not go beyond the schema in explaining parameter values or interactions. Baseline of 3 is appropriate because the schema does the heavy lifting.

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 uses a specific verb ('Get detailed information') and clearly identifies the resource ('a specific statistical classification entry by its ID'). It also distinguishes itself from the sibling tool list_classifications by indicating this tool retrieves details for one entry, not a list.

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 gives explicit usage guidance: 'Use list_classifications first to find the ID.' This tells the agent when to use this tool versus the sibling list tool and establishes the prerequisite step for invocation.

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