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

No annotations exist, so the description carries the full burden. It discloses that nothing is fetched (works offline), that only draft links with #d= are readable, and that kept links (#k=) cannot be read. It also describes the output shape, giving the agent a clear behavioral model.

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 structured logically: use case, what it decodes, output shape, behavior, limitation. Every sentence adds information, and there is no waste. It is longer than average but appropriate for the complexity.

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 one parameter and no output schema, the description covers all essential context: purpose, usage, parameters, output shape, and limitations. It references the sibling tool for output shape, which is sufficient. No critical gaps found.

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?

The schema already describes the link parameter with an example and notes that whole URL or fragment is acceptable. The description adds crucial semantic context about the #d= vs #k= distinction, which goes beyond the schema and clarifies what values will work, but the schema still does the heavy lifting.

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 clear use case ('Use when someone gives you a this trip, btw link and you need to know what is actually in it') and specifies the resource and action. It distinguishes itself from the sibling build_trip_link by stating it returns the trip in the same shape build_trip_link accepts, implying read vs build.

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?

Explicitly states when to use (to summarise, answer, add a stop, or convert) and clearly defines the limitation for kept links, which serves as a when-not-to-use. It references the sibling tool build_trip_link as the counterpart for building, providing a clear alternative.

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