alltrails_get_activity_feed

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

Adds behavioral detail beyond readOnlyHint annotation: defaults to signed-in user, can target public profiles, feed argument determines directory vs items, pagination via cursor. No contradictions.

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?

Two sentences, front-loaded with main action, no wasted words. Every sentence adds value.

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 5 parameters, no output schema, and only readOnlyHint annotation, description fully explains all relevant behavior: directory vs items, defaults, pagination, and compact mode.

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 covers 100% of parameters; description adds semantics: feed omission meaning, compact slim projections, cursor for pagination, and default userId behavior.

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?

Description clearly states it gets an activity feed (recorded hikes and posts), distinguishes from sibling tools that focus on profiles, trails, etc. Provides specific verb+resource with contextual details.

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?

Explains use of feed argument to get items versus omitting to get directory, and compact option for slim projections. No explicit when-not-to-use, but context is clear given sibling names.

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