list_invoices

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

No annotations are present, and the description adds no behavioral details such as pagination, default result limits, sorting, or the fact that filters are supported. It merely restates the function's basic action.

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 that front-loads the action and resource. No wasted words or redundant 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?

Given the tool has 9 optional filter parameters, no output schema, and no annotations, the description is too minimal. It fails to mention return format, pagination, or that the filters exist, making it inadequate for an agent to fully understand the tool's capabilities.

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 schema provides descriptions for all 9 parameters, covering 100% of them, so the baseline is 3. The description itself adds no parameter-level detail, but the schema already documents each filter and its format.

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 uses a specific verb 'List' with the resource 'invoices', and clarifies the source as the 'connected IntakeQ account'. It clearly distinguishes from the sibling tool get_invoice, which retrieves a single invoice.

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 provided on when to use this tool versus alternatives like get_invoice. The description does not mention whether this is for bulk retrieval, or mention any filtering or pagination considerations.

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