get_invoice_lookups

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

Annotations are absent. Description only notes 'Fails loudly,' hinting at error behavior but not explaining permissions, safety, or side effects. Minimal behavioral disclosure.

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?

Extremely short (two phrases), but the brevity omits important context. Some sentences could be added to improve guidance; current conciseness is not optimally helpful.

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?

With many sibling lookup tools and presence of an output schema, the description should explain what 'invoice lookups' returns or how it differs. Currently incomplete for effective use.

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?

No parameters in schema, so description does not need to add param meaning. Baseline of 4 is appropriate as there is nothing to clarify.

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 states 'Invoice lookups' which identifies the resource and action, but does not differentiate from many sibling lookup tools (e.g., get_expense_lookups, get_new_invoice_lookups). The verb is implied by the tool name.

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 on when to use this tool versus alternatives like get_invoice_allocations or get_new_invoice_lookups. The description lacks context for selecting this tool.

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