toreador_list_sessions

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

With no annotations, the description carries the burden. It explicitly states 'list' (implying read-only) and lists included data fields (status, tx hash, confirmations, timestamps). It does not disclose rate limits or further behavioral traits, but for a simple read operation, this is sufficient.

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?

A single, clear sentence with no extraneous words. Every phrase adds value: '50 most recent', 'ERC-20 payment sessions', 'authenticated account', and the list of included fields.

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 the simplicity (no parameters, no output schema), the description covers the essentials. However, it does not mention pagination or how to retrieve older sessions, which could be useful context. Overall adequate but not perfect.

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?

The input schema has zero parameters (100% coverage trivially). The description adds significant meaning by specifying the count (50 most recent) and included fields, which is valuable context beyond the empty schema.

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 lists the 50 most recent ERC-20 payment sessions for the authenticated account. It specifies the resource (sessions), verb (list), and scope (50 most recent, authenticated account), distinguishing it from siblings like create_session and generate_qr.

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 usage for viewing recent sessions but does not explicitly state when to use this tool versus alternatives like list_history. No when-not or alternative tools are mentioned, leaving room for improvement.

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