pc_plan_purchase

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

The description notes it returns 'exact REST scenario, method, path, and gotchas', providing some behavioral insight. However, with no annotations, it does not disclose if the tool triggers side effects or requires auth.

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?

A single, well-structured sentence that immediately conveys the tool's function without wasted words. It could be slightly shorter but is clear.

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 and no parameter descriptions, the description should provide more detail. It covers the output contents but omits input requirements and return format specifics.

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?

The description makes no mention of the two parameters (customerId, country) despite 0% schema description coverage. The schema itself provides no descriptions, so the agent must guess their purpose.

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 it returns an end-to-end purchase workflow with REST details, distinguishing it from sibling tools like pc_get_scenario which may be more generic. It uses a specific verb ('Return') and resource ('New Commerce purchase 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?

No guidance on when to use this tool versus alternatives like pc_get_scenario or pc_list_scenarios. The description does not mention prerequisites, context, or exclusions.

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