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

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered structurally. The description still adds real behavioral context beyond them: newest-first ordering, workspace scoping, and the exact return envelope with the fields each item carries.

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?

Three sentences, each doing distinct work: identity/scope first, capability and filters second, return contract last. No repetition of the title and no filler wording.

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 no output schema, the description compensates by spelling out {items, total, has_more} and per-item fields, and it covers all three optional filters. For a three-parameter, zero-required read tool this is sufficient to call correctly on the first attempt.

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%, so the description must carry parameter meaning, and it does: it names the four allowed status values and explains that limit/offset paginate. It omits the 1-100 bound on limit and any note about offset alignment, leaving a small gap against the bare schema.

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 the caller's road trips") plus scope qualifiers: caller-owned, active workspace, newest-first ordering. That scope clause is what separates it from a broader workspace-wide trip listing, so an agent can place it without opening the schema.

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 states the read context ("from their active workspace") and that filtering and paging are optional, which implies a browse use case. It never says when to prefer this over another listing tool, nor does it give exclusion conditions; usage is inferable rather than stated.

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