mark_as_sent_invoice_reminder

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

Annotations indicate this is a write operation (readOnlyHint=false) and non-destructive, but the description adds no extra behavioral context. It does not mention the effect of marking, reversibility, or whether any notification is sent. It adds 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 a single, concise sentence with no filler. It is front-loaded and efficient, though slightly under-specified for the reasons noted in other dimensions.

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 simple mutation tool, the description is adequate but incomplete. It does not mention the return value, how it relates to sibling tools, or what 'sent' means in terms of side effects. Given no output schema and the presence of similar tools, more context is needed to fully understand the operation.

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 descriptions for invoice_id and reminder_id, so the baseline is 3. The description adds no additional meaning beyond the schema, but it does not need to since the schema fully documents parameters.

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 'Mark reminder as sent' clearly states the action and target resource. It distinguishes the 'mark as sent' operation from 'send' or 'unsend' actions, though it does not explicitly reference sibling tools.

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 is given on when to use this tool versus alternatives like 'send_invoice_reminder' or 'mark_as_unsent_invoice_reminder'. The description fails to specify whether this tool only updates status or also triggers sending.

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