get_smart_query_plan

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

No annotations exist, so the description carries the full burden. It clarifies that the tool returns a plan (tool sequence, parameters, expected outcomes) and implies it does not execute the steps since it says to execute them manually. However, it does not explicitly state read-only status, permissions, or side effects, though these are likely irrelevant for a plan retrieval.

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 well-structured with clear sections: purpose, prerequisites, next steps, and example. Every sentence adds useful information without fluff. The example JSON is practical and space-efficient.

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 no output schema, the description sufficiently explains what is returned (complete tool sequence, parameters, expected outcomes). It also covers prerequisites, follow-up actions, and provides a usage example, making it fully complete for a simple single-parameter tool.

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% for the single 'query_name' parameter, so baseline is 3. The description adds value by including a concrete example ('Hot Leads Pipeline Analysis') and a sample JSON body, plus pointing to get_smart_queries for discoverable names, enriching the schema description.

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 states 'Get detailed execution plan for a specific smart query' with a specific verb and resource. It clearly distinguishes from sibling 'get_smart_queries' by focusing on a plan for one named query rather than listing queries.

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 states prerequisites ('Use get_smart_queries first') and next steps ('Execute the returned tool sequence manually'), giving clear guidance on when to use the tool and what to do after. This differentiates from alternatives and provides a workflow context.

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