pc_plan_reconciliation

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

With no annotations, the description must fully disclose behavior. It mentions a 'workflow' but does not clarify if the tool performs an action (e.g., triggers reconciliation) or merely retrieves workflow steps, nor does it mention auth requirements, side effects, or output structure.

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 a single sentence with no extraneous words. However, it is not front-loaded with a clear action; it reads as a noun phrase lacking a verb.

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 minimal parameters, the description should provide comprehensive context. It mentions a workflow but omits return values, prerequisites, and behavior, leaving significant gaps for an AI agent.

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 single parameter customerId has no schema description (0% coverage), and the description does not elaborate on its purpose, format, or constraints, providing no added value beyond the schema itself.

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 identifies the tool as an invoice reconciliation workflow with a specific process (invoice -> line items -> statement), distinguishing it from sibling tools focused on auth, purchase, or transfer. However, it lacks a direct action verb like 'reconcile' or 'get 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?

No guidance on when to use this tool versus alternatives. Sibling tools include pc_plan_purchase and pc_plan_transfer, but the description does not specify scenarios or exclusions, leaving the agent without context for selection.

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