list_invoices

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

Notes READ-ONLY but no annotations provided; description omits pagination behavior, default limits, ordering, or response structure, leaving significant gaps.

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 with front-loaded purpose. Efficient but could benefit from bullet points or clearer separation of read-only constraint.

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?

No output schema; description fails to mention return structure, pagination details, or error handling. Incomplete for a list operation with many optional filters.

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 covers 100% of parameters with descriptions. Description adds only generic 'filtering options' without enhancing parameter understanding beyond schema.

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?

Description clearly states it lists invoices with filtering options and notes read-only nature. However, it does not differentiate from sibling list_invoice_items or display_invoices_for_date.

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?

Mentions invoices must be created elsewhere, implying no create via this tool, but lacks explicit when-to-use vs. other invoice-related tools like get_invoice or get_patient_invoices.

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