cerebrochain-mcp-server

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

With no annotations, description carries full burden and succeeds in disclosing return behavior ('Returns cheapest and fastest options') and critical auth context ('Free — no API key needed'). Missing error handling or rate limit details.

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?

Three sentences with zero waste. Front-loaded with core action, followed by output behavior, then auth requirements. Every clause earns its place.

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?

Compensates for missing output schema by describing return values ('cheapest and fastest'). Input schema is fully documented. Could enhance by noting international support (country codes exist in schema) or dimensional 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?

Schema has 100% description coverage, establishing baseline 3. Description mentions 'package' which loosely implies dimensional relevance, but adds no syntax guidance, validation rules, or relationships between parameters (e.g., that dimensions are optional but affect accuracy).

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?

Excellent specificity with 'Compare shipping rates' verb, explicit carrier enumeration (UPS, FedEx, USPS, DHL), and clear resource ('package'). Distinct from siblings like track_shipment (tracking status) and optimize_route (routing logic).

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?

Implicit usage is clear (use when comparing rates), but lacks explicit when-to-use guidance versus siblings like track_shipment or list_shipments. No mention of prerequisites or exclusions.

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