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

With no annotations, the description carries full burden. It discloses network access ('THIS ONE TOUCHES THE NETWORK'), TLS usage, password semantics of the #k= phrase, credential handling, rate-limit consequences for wrong guesses, and that nothing is stored. This goes far beyond basic read/write hints.

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 long but every sentence adds necessary context—use case, return contents, network behavior, credential handling, and sibling differentiation. It is front-loaded with the primary purpose. A slight structural improvement (e.g., separating cautions) would earn a 5, but it remains efficient for the amount of critical information.

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 no output schema, the description fully explains return values (stops with dates, modes, track, lodging, notes, hand-drawn path). It also covers network, security, and alternatives, making it complete for a tool with inherent complexity around credentials and remote access.

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 covers the single parameter well (100% coverage), so baseline is 3. The description adds meaningful context: the #k= part is a password, the link must be sent over TLS, and the phrase should not be repeated or guessed. This enriches the parameter's meaning beyond its type/format.

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 use case ('Use when someone gives you a KEPT this trip, btw link') and states exactly what the tool does: retrieve the trip's contents for summarization, questions, or change checks. It explicitly contrasts with read_trip_link for draft links, distinguishing the tool from its sibling.

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 clearly states when to use this tool (for kept links) and when to use the alternative ('For a DRAFT link (#d=) use read_trip_link instead'), plus why (network vs. no network). This is explicit guidance with exclusions and an alternative named.

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