FreightUtils MCP Server

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

Adds data scope context (2,939 entries, 9 hazard classes) beyond name, but missing error handling, rate limits, or destructiveness info since no annotations provided.

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?

Front-loaded with purpose, followed by domain context, scope specifics, bulleted use cases, and parameter guidance; no redundant text.

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?

Comprehensive coverage of input intent and data points returned (hazard class, tunnel codes, etc.), though output format remains unspecified given lack of output schema.

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?

With 100% schema coverage, exceeds baseline by clarifying parameter relationship: 'UN number for exact lookup, or a search term for name-based search' (mutual exclusivity guidance).

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?

Specific verb 'Look up' + resource 'ADR 2025 database', clearly distinguishes from sibling 'adr_exemption_calculator' by positioning as database lookup vs calculation tool.

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?

Explicit 'Use this tool when you need to' section with 4 specific scenarios, but lacks 'when not to use' or explicit contrast with adr_exemption_calculator.

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