get_invoice_reminder

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

Annotations already convey read-only, open-world, and idempotent behavior. The description adds nothing beyond repeating the fetch action—no mention of error conditions, return format, or any domain-specific caveats, so it provides no additional transparency.

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 extremely short and has no filler, which is concise in structure. However, it is under-specified to the point of being unhelpful; the brevity sacrifices the clarity needed for effective tool selection. It strikes a poor balance between conciseness and informativeness.

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 getter, the description is still incomplete: it doesn't mention that both IDs are required, that it returns reminder details, or that it operates specifically on invoice reminders. Without the tool name and sibling context, an agent would be guessing at its behavior. The lack of output schema further increases the need for a richer description.

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%: both invoice_id and reminder_id have clear descriptions in the schema. The tool description doesn't add or enhance parameter meaning, but the schema fully documents them, so the 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?

The description 'Fetch a reminder' has a clear verb and a generic resource, but it doesn't specify that this is for invoice reminders or distinguish it from sibling tools like get_invoice_reminder_pdf or list_invoice_reminders. It's not a tautology, but it's vague about scope.

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 such as list_invoice_reminders or search_reminders. The description provides no context for when this is the appropriate choice.

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