Plan invoice reconciliation

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

The description adds meaningful behavioral detail beyond the readOnly/idempotent/non-destructive annotations: no Partner Center credentials are used, no network call is made, and it is a lookup over a bundled scenario pack. It also warns about v1 endpoint retirement, which is valuable operational context. No contradiction 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?

The description is front-loaded with the primary action and purpose, then layers in caveats, return format, and related-tool guidance. It is longer than a minimal description but every sentence adds value; the only minor inefficiency is some redundancy in the 'Planning only' clarification.

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 that the output schema exists and the description already covers purpose, usage boundaries, behavioral constraints, output structure, and next-step actions, the description is complete for an agent to select and invoke this tool correctly. No major operational gaps remain.

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?

There is only one parameter, customerId, and the input schema already fully documents it, including placeholder substitution behavior and omission semantics. The tool description itself does not add parameter-level detail, so the baseline of 3 applies due to 100% schema coverage.

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 opens with a specific verb and resource: 'Return the ordered invoice reconciliation workflow for a billing period' and enumerates concrete steps (locate invoice, read totals, pull line items, download statement). It clearly differentiates from sibling planning tools by naming its exact domain (billing and revenue reconciliation).

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 when to use it: 'Use this for billing and revenue reconciliation.' It also provides an exclusion, 'Planning only: nothing is executed,' and points to an alternative tool for related concerns: 'call pc_whats_new for the cutoff dates.' It additionally tells the agent how to proceed with returned steps via pc_generate_call/pc_get_scenario.

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