Iconsult MCP

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

With no annotations provided, the description carries full burden and does well by disclosing key behavioral traits: it's a read-only analysis tool (implied by 'critique' and 'analyzes'), deterministic rather than generative, returns structured issues with severity levels and suggestions, and explicitly states it makes no LLM calls. However, it doesn't mention performance characteristics, rate limits, or authentication requirements.

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?

The description is efficiently structured in three sentences: purpose statement, analysis dimensions, and behavioral constraints. Every sentence adds value with zero wasted words, and key information is front-loaded with the core function stated immediately.

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 analysis tool with no output schema, the description provides good context about what the tool does, how it works (deterministic structural analysis), and what it returns (issues with severity, categories, suggestions). The main gap is lack of output format details, but given the tool's relatively simple function and good behavioral disclosure, it's mostly complete.

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% with a single parameter clearly documented in the schema. The description doesn't add any parameter-specific information beyond what the schema provides (consultation_id as the session to critique), so it meets the baseline for high schema coverage without adding extra value.

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?

The description clearly states the tool performs a 'deterministic quality critique of a consultation session' with specific analysis dimensions (workflow completeness, traversal depth, pattern assessment coverage, passage diversity, critical edge checks). It distinguishes from siblings by focusing on structural analysis rather than generation, reporting, or planning functions.

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?

The description implies usage context ('analyzes logged steps') and distinguishes from LLM-based approaches ('No LLM calls — pure structural analysis'), but doesn't explicitly state when to use this versus alternatives like consultation_report or supervise_consultation. It provides some guidance but lacks explicit when/when-not comparisons.

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