Send signing reminder

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

Annotations indicate mutation (readOnlyHint=false) but no destructive or idempotent hints. The description adds minimal behavioral context: it sends a reminder. It does not disclose that reminders reuse the original email template (information is in schema descriptions but not in the description itself), nor does it mention side effects or rate limits.

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?

Single sentence, no wasted words. Directly communicates the tool's purpose without extraneous information.

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?

The description is adequate for a simple tool but lacks explanation of return values (though output schema exists) and does not mention default behavior (reminding all pending signers) or auto-detection of entity_type. It is minimally complete.

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% with all parameters described. The description does not add extra parameter meaning; it only states the overall action. Baseline 3 is appropriate since the schema already documents semantics.

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 explicitly states the verb 'send' and the resource 'signing reminder to pending signers on a document or document group'. It clearly distinguishes from siblings like 'send_invite' (initial invitation) by focusing on reminders for pending signers.

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 'pending signers' which implies not for completed documents, but it does not provide explicit guidance on when to use this tool versus alternatives like 'cancel_invite' or 'send_invite'. No when-not or exclusions are stated.

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