invoices_create_invoice_schedule

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

Annotations already indicate readOnlyHint=false, destructiveHint=false, and idempotentHint=false, so the agent knows it is a non-read-only operation. However, the description adds no further behavioral context, such as permissions required, what gets created, or any side effects. It simply restates the verb, contributing nothing beyond the 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 concise but under-specified. It is a single phrase that does not earn its place because it offers no information beyond the name. This is not effective conciseness but rather underspecification, similar to the 'Process' example.

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—19 parameters, nested objects, no output schema—the description is severely inadequate. It does not explain what an invoice schedule is, how the schedule object should be structured, or what the expected result might be. An agent has no context to construct a correct request.

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?

With schema description coverage at 47% (low), the description should compensate by explaining key parameters or their relationships. It provides none. The description is silent on all 19 parameters, leaving the agent to rely on a partially documented schema. No value is added.

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 'Create Invoice Schedule' is essentially a restatement of the tool name, with no additional specifics about scope, fields, or behavior. It does not distinguish the tool from siblings like 'invoices_create_invoice' or 'invoices_schedule_invoice_schedule', making it a tautology that adds no new meaning.

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 whatsoever about when to use this tool versus alternatives. No mention of prerequisites, side effects, or exclusions. An agent has to infer from the name alone, which is insufficient for selecting among many invoice-related tools.

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