FreightUtils MCP Server

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

With no annotations, description provides good domain context (what Incoterms define) but lacks tool-specific behavior details like output format, error handling for invalid codes, or rate limits.

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?

Well-structured with front-loaded purpose, logical flow, and bulleted use cases; listing all 11 codes is justified for input validation guidance.

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?

Adequate given simple schema, but lacks description of return values/output structure (no output schema provided) or authentication requirements.

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?

Adds valuable context beyond 100% schema coverage by listing specific valid codes (EXW, FCA, etc.) and mapping them to category values (any_mode vs sea_only).

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?

Clearly states the tool looks up 'Incoterms 2020 trade rules' and distinguishes from logistics-calculator siblings by defining unique domain (risk/cost transfer rules).

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?

Provides explicit 'Use this tool when' scenarios (explain meaning, compare responsibilities, check transport modes) though lacks explicit 'when not to use' or sibling comparisons.

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