alltrails_get_list_items

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

Beyond the readOnlyHint annotation, the description adds that items are sparse references, that compact=true returns slim entries sorted by order, and that the list id is numeric. No contradictions with annotations.

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 a single efficient paragraph. It front-loads the main purpose, then explains the nature of items and the compact option without any wasted words.

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?

With only two parameters and no output schema, the description fully covers what the tool does, the content of items, and how to proceed for full details. It references sibling tools appropriately.

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% (listId required, compact optional boolean). The description adds meaning beyond the schema by explaining that compact=true returns entries sorted by order, and that listId is numeric, which is not in the schema description.

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 gets trails saved in an AllTrails list by numeric list id, specifying that items are sparse references (trailId, order, notes) and not trail details. It distinguishes from siblings like alltrails_get_trail by noting the need for hydration.

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 explains when to use the tool (with a list id from alltrails_list_user_lists or alltrails_search) and suggests using alltrails_get_trail for full details. It could be improved by explicitly stating not to use this tool if full trail details are needed.

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