GroundTruth Dispatch

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. Description adds that output includes routing decision, confidence score, embedded routing table, and recommended next JSON call. No contradictions; valuable context beyond annotations.

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?

Information is well-structured with clear headings and examples. Slightly verbose with repeated examples but front-loaded purpose. Every sentence serves a purpose.

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 routing tool with 13 siblings, description explains input, output, and usage boundaries. Lacks output schema but defines output structure in text. Completeness is adequate given annotations handle safety.

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 coverage is 100% with both parameters described. Description adds concrete examples for 'query' and clarifies 'projectPath' defaults to current working directory. Adds value beyond schema but not extensive.

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 the tool routes plain-text queries to appropriate gt_* tools. Uses specific verb 'routes' and resource 'user query', and distinguishes from siblings by positioning itself as the dispatcher when intent is ambiguous. Examples reinforce exact usage.

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?

Explicit 'WHEN TO USE' and 'WHEN NOT TO USE' sections. States to use when intent is ambiguous or 'use gt' invoked without tool, and not to use when tool is already known. Provides clear alternative (direct call) to save round-trip.

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