list_conversations

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

With no annotations, the description carries the behavioral transparency burden. It does disclose meaningful behavior: the operation is a GET (read-only) and nested Reservation objects are denylist-stripped. However, it omits pagination, response format, auth expectations, and error behavior, so transparency is partial.

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 definition is two short sentences, action first, with no filler. The endpoint and the denylist-stripping caveat are both useful and earn their 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 two undocumented optional parameters, no output schema, and no annotations, this is incomplete. It does not explain what listingId and reservationId do, how results are paginated or ordered, or what the response looks like, and it lacks sibling disambiguation.

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%, and the description never mentions listingId or reservationId or how they affect the result. The schema provides only names and types, so the agent must guess the filter semantics. The only query parameter mentioned, includeResources=1, is part of the endpoint, not one of the input-schema parameters.

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 names the action ('List') and the resource ('inbox threads'), and pins it to the exact endpoint 'GET /v1/conversations?includeResources=1'. This makes it semantically distinct from siblings such as list_reservations or list_messages, which target different resources.

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?

There is no guidance on when to choose this tool over list_reservations, list_messages, or inbox_triage. No exclusions, prerequisites, or alternative conditions are stated. 'List inbox threads' gives only an implicit use case.

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