list_transactions

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'List all transactions' implies a read-only operation but does not disclose return format, pagination, potential error conditions, or any side effects, leaving the agent uninformed about runtime behavior.

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 a single, short sentence with no superfluous information. It is highly concise and directly to the point, satisfying the requirement that every word earns its place.

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?

For a tool with no parameters, no annotations, and no output schema, the description is minimal but not entirely insufficient. It clearly states the action, but it does not clarify what 'all transactions' means in context, potential result size, or any limitations, leaving room for ambiguity.

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?

This tool has zero parameters, so the schema is an empty object. The baseline score of 4 is appropriate because there are no parameter details to explain, and the description adds no meaning beyond the fact that all transactions are listed without any filters or inputs.

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 'List all transactions' clearly states the verb and resource, making it obvious that this tool lists transactions. It distinguishes from the sibling 'get_transaction' which retrieves a single transaction, but it does not specify the scope or criteria for 'all', leaving some ambiguity.

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 alternatives. There is no mention of exclusions, prerequisites, or situations where a different listing tool might be more appropriate, despite the presence of siblings like 'list_contracts'.

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