get_transaction_lookups

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

The description notes 'Fails loudly,' which informs the agent of the failure behavior. However, with no annotations provided, the description carries the full burden and lacks details on success conditions, output nature, or what triggers failure.

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 but includes a version notation '[Not in LCS /v1]' that may be irrelevant for an AI agent. While concise, it could be more informative without adding length.

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 0 parameters and an existing output schema, the description is minimal but adequate for a simple lookup tool. However, the lack of clarity on what is looked up and the presence of many similar siblings reduces completeness.

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 the baseline is 4. The description adds no parameter information, but none is needed.

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 'Transaction lookups' which indicates the tool retrieves lookup data for transactions, but is vague and does not specify what kind of lookups or distinguish it from siblings like get_expense_lookups or get_invoice_lookups.

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 other lookup tools (e.g., get_expense_lookups, get_invoice_lookups). The description does not mention context or alternatives.

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