list_domain

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

No annotations are provided, so the description carries the full burden. It implies a read-only operation (listing files) but does not disclose behavioral traits such as whether data is sorted, paginated, or if any side effects occur. No mention of authentication, permissions, or rate limits.

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 front-loaded with the purpose and includes a clean arg list. Every sentence adds value with no redundancy. Could be slightly more concise by omitting 'Args:' label, but overall efficient.

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 that an output schema exists, the description does not need to detail return values. It covers parameter semantics adequately and implies the tool is for enumeration. However, it lacks context on sorting, pagination, or how to handle large result sets, which is reasonable for a listing tool.

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 well by explaining the domain parameter with explicit allowed values, date parameters with format hints, and max_results with a default. This adds significant meaning beyond the raw 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 files in a domain with metadata and summaries, using the specific verb 'List'. It mentions allowed domain values (sessions, transcripts, notifications), which clarifies scope. However, it does not explicitly differentiate from sibling tools like 'search' or 'summary', 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 notes that date parameters are optional and max_results has a default, but provides no guidance on when to use this tool versus alternatives (e.g., 'search' or 'read'). It does not specify prerequisites or conditions for use.

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