lb_wallet_get_transactions

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

The description adds behavioral context beyond the readOnlyHint annotation by detailing pagination behavior and the note about legacy entries exceeding per_page count. This helps the agent anticipate edge cases.

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?

Two sentences efficiently convey the core function and a critical behavioral nuance (legacy entries). No extraneous words; front-loaded with the primary action.

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 paginated list tool with good annotations and full schema coverage, the description is largely complete. It might have benefited from mentioning the return format, but the key behavioral constraint (legacy entries) is included.

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 coverage is 100% with standard parameter descriptions. The description mentions pagination generally but does not add new semantics beyond what the input schema already provides for page and per_page.

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 clearly states the tool retrieves 'Listing Bureau wallet transaction history' with pagination, distinguishing it from sibling tools like lb_wallet_get_balance. The verb 'Get' and specific resource make the purpose unambiguous.

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 implies paginated retrieval but does not explicitly contrast with alternatives. However, sibling tools have distinct purposes (e.g., balance, orders), so usage context is clear, lacking only explicit 'when not to use' guidance.

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