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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, and the 'Safety: Closed-world' sentence simply restates openWorldHint=false. The one genuine addition is the requirement that clients convert UTC starts_at/ends_at into the activity timezone for display, which is real behavioral context the annotations and schema do not convey.

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 content is complete and relevant to the activity model, but it is poorly structured: a 45-item slug wall dominates the text, and creation-only guidance is interleaved with listing concerns rather than being front-loaded or separated.

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 not be explained, and the mutation/write concerns are largely covered elsewhere. What is missing for a list tool is any statement of default filtering, result size or ordering, and how the broad filter set interacts with trip_id scope, leaving the definition only minimally adequate.

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%, so baseline is 3, and the description does add genuine value by enumerating valid activity_type slugs and explaining that custom category slugs come from tripsy_categories_list and are valid only on Activity objects. However, it spends significant space on provider_reservation_code and latitude/longitude, which are not parameters of this tool, diluting the useful signal.

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 opening line 'Scheduled or unscheduled trip activities' names the resource but never states a verb like list/retrieve, so the read operation is only inferable from the tool name. Much of the body discusses activity creation (one activity per stop, latitude/longitude required), which blurs rather than sharpens what this listing tool does.

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?

'Supports common list filters' implies filtered retrieval but names no filter, ordering, or pagination behavior. There is no guidance on when to use this versus tripsy_activities_show or the related list tools (expenses_list, hostings_list), so the agent must infer the choice from names alone.

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