Conclave 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 the behavioral outcome ('clear custom selection', 'return to tier-based config', 'queries will use tier parameter') and return value ('Confirmation that custom selection was cleared'), though it lacks details on permissions or 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?

It is front-loaded with the core action in the first sentence, followed by outcome and return details in clear, efficient sentences. Every sentence adds value without waste, making it highly concise and well-structured.

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 the tool's simplicity (0 parameters, no annotations, but has output schema), the description is nearly complete by explaining the reset action, post-reset behavior, and return value. It could slightly improve by mentioning any prerequisites or errors, but covers essentials well.

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?

The tool has 0 parameters with 100% schema description coverage, so no parameter info is needed. The description appropriately focuses on behavior and output, earning a baseline 4 for not adding unnecessary details beyond the empty schema.

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 specific action ('Clear custom conclave selection') and the resource affected ('tier-based config'), distinguishing it from siblings like conclave_config or conclave_select that likely configure or choose models rather than resetting to defaults.

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?

It implicitly indicates usage context ('return to tier-based config') and the effect ('queries will use the tier parameter'), but does not explicitly state when to use this vs. alternatives like conclave_config or what triggers a reset need, missing explicit exclusions or prerequisites.

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