mark_paid_scheduled_charge

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

No annotations provided, so description carries full burden. It discloses allowed statuses and that future cycles continue, but does not mention side effects, reversibility, or webhook implications. Adequate but could be more explicit.

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?

Two sentences, front-loaded with action and context. Every word earns its place; no fluff. Highly 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 complexity (one-time vs recurring, status conditions, 4 parameters), the description covers essentials for tool selection. No output schema needed due to simple nature. Could mention reversibility but not critical.

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%, and description adds value by explaining when cycleNumber is required vs. omitted, and paymentDate format constraint. ExternalReference is clarified. Adds nuance beyond schema.

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?

Description clearly states 'Manually mark a scheduled charge as paid' and differentiates between one-time and recurring usage, with specific conditions. This verb+resource+scope is precise and distinguishes from sibling tools.

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?

Description provides explicit scenarios: for one-time (omit cycleNumber) and recurring (pass cycleNumber) and allowed statuses (due_today, overdue, failed). It lacks alternative tool mentions but context is clear enough for agent decision.

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