create_invoice_reminder

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

Annotations already indicate this is a non-read-only, non-destructive operation, but the description adds no behavioral detail. It does not explain what 'create reminder' entails (e.g., scheduling, notification, persistence), side effects, or how it relates to the invoice lifecycle. No contradiction with annotations, but no added value either.

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 only two words, which is under-specification rather than effective conciseness. It does not earn its place by providing useful distinguishing information; it merely abbreviates the tool name.

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?

Despite having a single parameter and annotations, the description lacks essential context for a mutation tool. It fails to state the purpose of an invoice reminder, when to create one, or what happens after creation. The agent is left to infer behavior from the name alone.

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% (invoice_id well-documented), so the baseline is 3. The description provides no additional parameter semantics, but none are needed given the single simple parameter.

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 reminder' is essentially a tautology of the tool name 'create_invoice_reminder', but it omits the crucial 'invoice' context. It neither specifies the resource precisely nor distinguishes the tool from many sibling invoice-related tools (e.g., create_invoice, create_invoice_payment).

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 like send_invoice_reminder or mark_as_sent_invoice_reminder. No prerequisites, conditions, or exclusions are mentioned, leaving the agent without context for appropriate invocation.

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