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. It compensates by describing return values ('full item details including stock, location, and pricing') and auth requirements ('Requires API key'), but omits rate limits, error behaviors, or idempotency declarations.

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 tightly constructed sentences with zero waste: action definition, return value disclosure, and auth requirement. Information is front-loaded with the primary verb and scoping.

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?

Given low complexity (1 string parameter, no nested objects, no output schema), the description adequately covers the operation's contract. It explains what is returned in lieu of an output schema, though error handling (e.g., invalid SKU) remains unspecified.

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% ('SKU code to look up'), establishing baseline 3. Description reinforces this with 'by its SKU code' but adds no additional semantic context like format constraints (e.g., alphanumeric length) or validation rules.

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?

States specific verb ('Look up'), resource ('inventory item'), and method ('by its SKU code'). Implicitly distinguishes from sibling 'search_inventory' by emphasizing exact SKU lookup versus general search, though it could explicitly name the alternative.

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?

Mentions 'Requires API key' as a prerequisite but provides no guidance on when to choose this tool versus siblings like 'search_inventory' (for partial matches) or 'check_stock_levels' (for stock-only queries). No explicit when/when-not conditions.

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