get_expense_lookups

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

The description mentions 'Fails loudly' which hints at error behavior, but no annotations exist. It does not disclose read-only nature, side effects, or other behavioral traits beyond the cryptic failure note.

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 very short, which could be concise, but it front-loads a cryptic platform note '[Not in LCS /v1]' that adds confusion rather than clarity. The message is fragmented.

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 an output schema present, the description need not detail return values, but it fails to specify the scope of the lookups. Among many sibling lookup tools, the lack of specificity leaves agents unsure when to call this one.

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?

There are no parameters, so schema coverage is 100%. The description adds no parameter info because none exist, but it could have clarified what the lookup results contain. Given zero params, it meets minimum baseline.

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 'Expense lookups' which identifies the resource but is vague. It does not differentiate from sibling tools like get_new_expense_lookups or get_hard_cost_expense_lookups, and fails to specify what kind of lookups are returned.

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 related tools. There is no mention of preconditions, alternatives, or scenarios where it should be preferred.

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