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

Beyond the readOnly/idempotent/non-destructive annotations, the description adds real behavioral facts: entitlement rules (Pro for owners, permission-based access for collaborators) and that full original email content plus attachments are returned by the API. The security note about treating email content as untrusted data is genuinely useful for an agent handling returned content. The 'Safety: Closed-world' sentence largely restates openWorldHint=false, which is redundant but not harmful.

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 scope statement is front-loaded and the sentences are dense but purposeful: listing behavior, permissions, and untrusted-content handling. The closing 'Safety: Closed-world' line duplicates the openWorldHint annotation and could be dropped without losing 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?

An output schema exists, so return values need no explanation, and the description covers the remaining gaps: pagination ('every page'), parent scoping rules, aggregation semantics, and access prerequisites. Nothing an agent needs in order to invoke this correctly is missing.

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 100%, so all three parameters already explain themselves, including the parent_id/parent_type dependency. The description reinforces that trip-level lists aggregate attachments across the trip but adds no syntax, format, or edge-case detail beyond what the schema states. Baseline 3 is appropriate when the schema carries the parameter burden.

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 opens with a specific verb and resource ('List every page of booking emails') and scopes it to attachments anywhere in a trip or on one activity/hosting/transportation, which separates it from a single-email fetch like tripsy_emails_show. It does not name that sibling explicitly, so the differentiation is implied by the list-vs-show naming rather than stated.

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?

It gives concrete conditional guidance: parent_id is required for activity/hosting/transportation and omitted for trip, and trip-level listing aggregates the whole trip. It also spells out who may call it (owners need active Pro; collaborators need document visibility permission and can call without Pro), which is exactly the pre-call context an agent needs. It stops short of pointing at related tools for other email workflows.

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