send_invoice_reminder

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

Annotations already mark this as non-read-only and non-idempotent, but the description adds no behavioral details. It does not disclose side effects like sending an email, updating reminder status, or triggering notifications, nor does it mention any authorization or trial-period constraints not in the schema.

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?

A single sentence is short, but this is under-specification rather than conciseness. The phrase "Send a reminder" adds no value beyond the tool name and lacks the necessary detail to guide correct invocation.

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 5-required-parameter write action with no output schema and many closely related sibling tools, this description is completely inadequate. It provides no information about return values, side effects, or relationship to other reminder/invoice operations, making it nearly useless for an agent.

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?

The description provides zero parameter explanation, but the input schema already covers 80% of parameters with meaningful descriptions (invoice_id, reminder_id, recipient_email, message). The missing subject parameter is not addressed, and the description does not compensate for any schema gaps, so baseline 3 is appropriate.

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 "Send a reminder" is a tautology of the tool name send_invoice_reminder, providing no additional specificity. It fails to mention the invoice context or distinguish itself from siblings like send_invoice or mark_as_sent_invoice_reminder.

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?

No guidance on when to use this tool, what prerequisites exist (e.g., invoice and reminder must exist), or how it differs from alternative reminder-related actions. The description offers no context for selection among similar tools.

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