mycelium_ask

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

No annotations provided, so description carries full burden. It details that lookups return answers with zero model calls and no context spent, and open-ended questions are marked for investigation. Also covers escalation due to ambiguity.

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 paragraphs, each sentence adds value. Front-loaded with purpose, no fluff, well-structured for quick comprehension.

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 param, no nested objects, output schema exists), description fully explains behavior, routing logic, and when to use alternatives. No gaps.

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?

Single parameter 'question' with schema coverage 100%. Description adds meaning by explaining how the question is processed (lookup vs. investigation), which is beyond the schema's description of 'The user's question, in their own words.'

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's purpose: "Route a question and answer it if it does not need deliberation." It specifies that it handles lookups directly and escalates open-ended questions, distinguishing it from sibling mycelium_forage.

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?

Explicitly says "Start here for every question." Provides examples of when to use (lookups) and when not (open-ended questions requiring mycelium_forage). Also advises resolving ambiguity before investigating.

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