list_paid_invoices

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

No annotations are provided, so the description must fully disclose behavior. It only states the action without mentioning read-only nature, pagination, sorting, or any side effects. This is insufficient for an agent to understand the tool's behavior.

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, clear sentence with no wasted words. However, it could be expanded to include parameter usage without losing conciseness. It earns points for efficiency but loses slightly for missing critical info.

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?

Despite having only one parameter and an output schema, the description lacks guidance on usage context (e.g., filtering, pagination). Given the large set of sibling tools, more context is needed to disambiguate use cases.

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 only parameter 'top' has a default of 0 but no description in the schema or the tool description. With 0% schema coverage, the description should explain the parameter's purpose and effect, but it does not, leaving the agent without guidance.

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 'List all fully paid invoices' uses a specific verb and resource, clearly distinguishing it from siblings like 'list_unpaid_invoices' and 'list_partially_paid_invoices'. It immediately conveys the exact scope of the 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 implies use when needing fully paid invoices, but it does not explicitly state when to use this tool over alternatives like 'list_invoices' (which likely returns all invoices). No exclusions or prerequisites are given.

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