invoice_reminder

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

No annotations are provided, so the description must fully describe behavior. It explains tone variation by reminder number and the draft limit benefit, but does not disclose other important aspects such as whether the tool sends the email or just generates text, or any required permissions. This is adequate but not comprehensive.

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 sentences long, with the purpose front-loaded. It is concise, uses clear language, and every sentence provides relevant information without redundancy. There is no wasted text.

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 lack of output schema and annotations, the description covers the basic purpose and a key behavioral trait (tone variation), but it does not explain what the output looks like (e.g., a full email draft) or provide enough context to fully understand the tool's capabilities relative to its many siblings. It is adequate but incomplete.

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 input schema has 100% description coverage, so the baseline is 3. The description adds no additional meaning beyond what the schema already provides for each parameter, such as the meaning of 'reminder_number' (which is already described in the schema). Thus, it does not improve parameter understanding.

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 tool writes polite and firm reminders for overdue invoices, and explains how tone varies by reminder number. However, it does not explicitly distinguish this tool from similar siblings like late_payment_reminder or payment_reminder_email, making it slightly less clear when to choose this specific tool.

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?

The description mentions that the tool does not count against a monthly draft limit, which is a useful constraint. However, it provides no guidance on when to use this tool versus its many siblings that also handle payment reminders (e.g., late_payment_reminder, payment_overdue_final_notice_email). This omission limits its utility for correct tool selection.

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