FreightUtils MCP Server

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

No annotations provided, so description carries full burden. Lists covered container types and calculation capability, but omits behavioral details like: validation logic when items exceed capacity, whether weight limits are enforced, or if calculations are optimistic (3D bin packing) vs simple volume division.

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?

Efficient structure with purpose statement, coverage list, usage triggers, and parameter instructions. Every sentence earns its place; no redundancy. Well front-loaded with the core value proposition.

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?

Appropriate for a 6-parameter tool with 100% schema coverage. Covers primary use cases and acknowledges the 'omit to list all' behavior via schema. Minor gap: doesn't clarify output format or calculation methodology (e.g., whether it accounts for pallet stacking inefficiencies).

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 has 100% coverage, but description adds valuable usage logic: 'Provide a container type for specs' vs 'Add item dimensions... to calculate loading.' This clarifies the optional parameter grouping (type only for specs, dimensions+weight+quantity for loading calc) better than the schema's zero-required-params structure.

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?

Opens with specific verb+resource ('Get ISO shipping container specifications and calculate loading') and explicitly enumerates the 10 container types covered. Distinguishes from generic calculator siblings by specifying ISO container focus.

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 you need to:' section with three concrete scenarios (dimensions/capacity, pallet fitting, item loading). Lacks explicit 'when not to use' guidance or differentiation from siblings like pallet_fitting_calculator or cbm_calculator.

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