invoices_delete_invoice_schedule

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the description adds no extra information about side effects (e.g., whether the schedule is permanently removed, what happens to associated invoices). The description merely repeats the verb 'delete' without disclosing consequences beyond what annotations already imply. No contradiction, but no additional value.

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 overly terse—just two words. While it is short, this is under-specification rather than concise efficiency. It lacks any structured detail, making it hard for an agent to know the full scope of the operation.

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?

For a destructive operation with three parameters and no output schema, the description is seriously inadequate. It does not mention what a schedule is, what happens on deletion, potential side effects, or any restrictions. The agent would need to infer everything from the name and schema, which is insufficient.

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 100%, so all three parameters (altId, altType, scheduleId) are already documented in the schema. The description provides no additional parameter semantics or usage hints. Baseline 3 is appropriate given the schema does the heavy lifting.

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 the verb 'delete' and resource 'schedule', which is clear at a basic level, but it lacks specificity about the schedule type (invoice schedule) and does not differentiate from semantically close siblings such as invoices_cancel_invoice_schedule or invoices_update_invoice_schedule. The tool name provides the invoice context, but the description itself is too terse to uniquely identify its purpose.

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 alternatives. The description gives no context about prerequisites, whether to prefer this over cancel or update operations, or any exclusions. An agent would have no clue when to invoke this against the many other schedule-related tools.

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