paypal_list_invoices

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

No annotations are provided, so the description must disclose behavioral traits. It only mentions routing and that arguments are a JSON string. It does not disclose whether the tool is read-only, what data it returns, pagination behavior, or any limitations. This is insufficient for a tool with no 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 extremely concise at three lines, covering purpose, routing, and parameters. It is front-loaded with the tool name and operation. However, it sacrifices substance for brevity, which may be acceptable if effective, but here it lacks critical details.

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 no annotations, no schema description coverage, and an output schema exists but is not mentioned, the description is incomplete. It fails to explain return values, how to construct the arguments JSON, or any context about invoice listing behavior.

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 description coverage is 0% (no parameters documented in schema beyond name and type). The description adds only that 'arguments' is a JSON string, but does not explain the expected keys, values, or structure. This does not compensate for the lack of schema documentation.

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 tool name 'paypal_list_invoices' clearly implies listing invoices, and the description confirms it's a PayPal connector operation. However, the description does not elaborate on what 'list' means (e.g., all invoices, filtered), lacking differentiation from sibling tools like quickbooks_list_invoices or xero_list_invoices.

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 provides no guidance on when to use this tool versus other listing tools (e.g., paypal_list_transactions, paypal_list_payouts) or general search/filter alternatives. No context about prerequisites or typical use cases.

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