get_new_expense_lookups

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

No annotations are provided, so the description must disclose behavior. It only says 'Fails loudly,' which hints at error behavior but does not explain why, when, or how it fails. No information about read/write nature, permissions, or side effects is given.

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 short, but it sacrifices clarity for brevity. It lacks essential information and is not 'front-loaded' with useful cues. Every sentence should add value; here, one sentence is vague and the other ('Fails loudly') is cryptic.

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 complexity of sibling tools and the existence of an output schema (not shown), the description is severely incomplete. It does not explain what 'lookups' means, what the output contains, or how the parameter affects results. The tool appears to be a lookup for new expenses, but critical context is missing.

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 input schema has one parameter ('matter_id') with 0% coverage (no description in the schema). The tool description does not explain the purpose or effect of this parameter, leaving the agent without guidance on how to use it.

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 states 'New-expense lookups,' which vaguely suggests it provides lookup data for creating a new expense, but it is not specific about what kind of lookups (e.g., expense types, categories). The phrase 'Fails loudly' adds ambiguity. Compared to siblings like 'get_expense_lookups' and 'get_hard_cost_expense_lookups,' the distinction is unclear.

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 siblings. No conditions, prerequisites, or exclusions are mentioned. The description leaves the agent to infer usage from the name alone.

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