Plan the calls that produce a scenario's parameters

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

Annotations already indicate read-only and non-destructive behavior. The description adds valuable context beyond annotations: 'Planning only: nothing is executed, no credentials are used, no network call is made.' This clarifies safety and side-effect-free behavior, consistent with 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?

Every sentence serves a distinct purpose: main function, scope, alternatives, rationale, and safety. No redundant or filler content; well-structured and front-loaded.

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?

The description covers purpose, usage guidance, alternatives, and safety considerations. With a full input schema and output schema present, all necessary context for an AI agent to select and invoke the tool is provided.

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 description coverage is 100%, so parameters are well-documented in the schema. The description only references 'parameters you have to supply yourself' conceptually, adding little semantic detail beyond what the schema already provides.

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 function: 'Given any scenario, return the ordered calls that produce the ids its path needs, plus the parameters you have to supply yourself.' It also distinguishes itself from sibling tools by emphasizing it works for 'every operation in the pack, not just the ones with a hand-written workflow.'

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 provides when-to-use and alternatives: 'For a business sequence and its preconditions prefer the curated planners' and lists all sibling curated planners. It also clarifies the tool's niche: 'This one only resolves parameters, which is why it works everywhere.'

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