cerebrochain-mcp-server

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

No annotations provided, so description carries full disclosure burden. Successfully notes operational constraints (API key, premium status) and calculation factors. Missing safety classification (read-only vs state-modifying), rate limits, and output format disclosure expected for computation tools without annotation coverage.

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?

Four tight sentences with zero redundancy. Front-loaded with core purpose ('AI-powered route optimization'), followed by specific factors, then operational constraints. Every sentence delivers distinct value (function, factors, cost, auth).

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 for the complexity given 100% schema coverage, but gaps remain due to missing output schema and annotations. Description omits return value structure (sequence? costs? map?) and safety hints (idempotent? read-only?) that would complete the operational picture.

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 coverage is 100%, establishing baseline 3. Description references 'capacity' and 'time windows' confirming input utilization but adds no syntax details, validation rules, or semantic relationships beyond what the schema already documents.

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?

Description provides specific verb ('calculates') and resource ('delivery route'), explicitly listing optimization factors (traffic, capacity, time windows, fuel costs). Clearly distinguishes from sibling 'compare_shipping_rates' (pricing vs routing) and 'get_optimization_recommendations' (advice vs calculation).

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 operational context via 'Premium tool' and 'Requires API key', implying cost and authentication prerequisites. However, lacks explicit when-to-use guidance versus alternatives like 'compare_shipping_rates' or exclusions for simple routing scenarios.

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