adr_exemption_calculator

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, so safety profile is clear. The description adds value by explaining the calculation logic (points = quantity x multiplier) and transport categories, but doesn't need to rehash annotations.

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?

Description is well-structured with a clear introductory line, followed by background and usage guidelines. No redundant sentences; each part serves a purpose. Front-loaded with key 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?

Given no output schema, the description adequately explains what the tool returns (points and exemption status) through context. It covers single and multi-substance cases, and provides enough detail for correct usage.

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 coverage is 100% with descriptions for all parameters. The description adds context on usage: un_number+quantity for single substance, items array for mixed loads, and explains the underlying concept. This goes beyond schema-only documentation.

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 clearly states it calculates ADR 1.1.3.6 exemption thresholds for mixed hazardous loads, with specific verb 'calculate' and explicit resource. It distinguishes itself from sibling tools like adr_lookup and adr_lq_eq_check by focusing on exemption calculation.

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?

Explicitly provides when-to-use scenarios: 'Check if a load qualifies', 'Calculate total ADR points', 'Determine if full ADR compliance required'. Also explains differentiation: single substance vs mixed loads, and contrasts with other tools implicitly.

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