invoices_auto_payment_invoice_schedule

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

Annotations already indicate readOnlyHint=false (write operation) and destructiveHint=false, so the description adds little beyond the word 'Manage'. It does not disclose side effects, such as whether changing autoPayment.enable toggles payment processing, or if there are any irreversible changes. The description carries minimal behavioral disclosure.

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 concise (one sentence) and front-loaded with the action. However, it is grammatically flawed ('an schedule' instead of 'a schedule') and lacks specificity. While there is no filler, the brevity comes at the cost of clarity, making it under-specified rather than effectively concise.

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 the tool's complexity (nested autoPayment object, multiple required parameters like scheduleId and id, no output schema), the description is inadequate. It does not mention required inputs or the expected outcome (e.g., returns the updated schedule). It fails to explain what 'manage' entails, leaving an agent without enough context to call it correctly.

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 80%, meaning most parameters have at least a short description (e.g., scheduleId as 'Schedule Id', autoPayment as 'auto-payment configuration'). The description adds no additional semantic meaning beyond the schema. It does not explain the role of autoPayment.enable or the meaning of nested fields like paymentMethodId, so it remains at the baseline for partially covered 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?

The description states 'Manage Auto payment for an schedule invoice', which indicates the tool deals with auto-payment on an invoice schedule. However, the verb 'Manage' is vague and doesn't specify the exact operations (enable, disable, update payment method). It doesn't explicitly distinguish itself from sibling tools like invoices_update_invoice_schedule, though its focus on auto-payment is implied.

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?

There is no guidance on when to use this tool versus alternative invoice-related tools. No mention of conditions, exclusions, or comparison to siblings such as invoices_update_and_schedule_invoice_schedule or invoices_schedule_invoice_schedule. The description leaves the agent to infer usage context.

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