cerebrochain-mcp-server

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

With no annotations provided, the description carries the full burden. It adds valuable behavioral context: 'real-time' nature, specific return data fields (compensating for missing output schema), and authentication requirements. However, it omits rate limits, error behaviors, and side effects.

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?

Two sentences with zero waste. Front-loaded with action and resource ('Get real-time tracking for a shipment route'), followed by specific data points and auth requirement. Every word 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?

For a single-parameter tool with no annotations or output schema, the description adequately compensates by previewing return values (location, progress, ETA, stops) and noting the API key requirement. Sufficient for agent invocation decisions despite missing error documentation.

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 description coverage is 100% for the single 'route_id' parameter, establishing a baseline of 3. The description does not add syntax details, format constraints, or examples beyond what the schema already provides.

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?

Clear verb ('Get') + specific resource ('shipment route') with enumerated data points (location, progress, ETA, stops). Distinguishes from siblings like list_shipments (specific tracking vs. listing) and optimize_route (tracking vs. optimization), though it doesn't explicitly clarify the difference from get_order_status.

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?

States 'Requires API key' indicating a prerequisite, but provides no guidance on when to select this tool versus alternatives like get_order_status or list_shipments. No mention of input prerequisites (e.g., valid route_id format) or error conditions.

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