list_lease_transactions

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

With no annotations, the description carries the full burden. It discloses the return type ('Dictionary with transactions list') and pagination behavior via limit/offset defaults. It does not mention ordering, error conditions, or explicitly state it is a read-only operation.

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 succinct, structured with Args and Returns sections, and front-loaded with the main purpose. Every sentence adds value, with no redundant information.

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 simple list tool with an output schema present, the description covers the core purpose, parameters, and return type. It lacks edge-case details like ordering or filtering options, but these are not critical for basic invocation.

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?

Schema description coverage is 0%, so the description compensates by explaining each parameter: lease_id as 'The lease ID', limit as 'Maximum number of results', offset as 'Offset for pagination'. This adds meaningful context beyond the raw schema types and defaults.

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 'List transactions for a specific lease' with a clear verb, resource, and scope. It distinguishes from sibling tools like list_bank_account_transactions and list_leases by specifying lease-specific transactions.

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?

Usage is implied by the purpose: to list transactions for a lease. However, it does not explicitly mention when to use this tool over alternatives or provide any exclusions. There is no reference to related tools like list_bank_account_transactions.

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