consult

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

No annotations provided. Description mentions sending prompt and returning response, and lists agents/personas, but does not disclose rate limits, costs, idempotency, or error behavior. The timeout parameter is not explained.

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?

Very concise: 3 sentences plus bullet list. No fluff. Clear structure with sections for description, use cases, and available values.

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?

Description covers purpose and valid parameter values for agent/persona, but lacks details on return format, error handling, and timeout behavior. Output schema not provided, so return value info is minimal.

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 has 0% description coverage. Description adds value by listing valid agents and personas, which are not enum constrained in schema. However, it does not describe timeout_seconds or prompt format. Partially compensates for schema gaps.

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 clearly states: 'Send a prompt to one CLI agent and return its response.' It lists use cases and available agents/personas. However, it does not explicitly differentiate from sibling tools like consult_parallel, which could cause confusion about when to use which.

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 use cases (quick second opinion, ask specific model, get help from specialist). Does not include when NOT to use or explicitly mention alternatives among siblings (e.g., consult_parallel for parallel queries).

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