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

Annotations already establish readOnly, idempotent and non-destructive behavior, so the bar is lower. The description adds genuinely new context: the output is the standard unedited list regardless of user customisation, it is free with no signup, and it is explicitly contrasted with the customisable share_checklist path. It stops short of saying whether the return is a file, bytes or a URL.

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?

Front-loads what the tool returns, then the scope caveat, then the alternative — three sentences with no filler. The IMPORTANT marker correctly flags the sentence an agent must not miss, and nothing is repeated from the schema or annotations.

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?

For a one-parameter read tool with full annotation coverage and no output schema, the description covers scope, eligibility and routing completely. The only gap is the shape of the return value (file, stream or download link), which matters for a PDF-producing tool but is not stated.

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%, making 3 the baseline, but the description goes further by enumerating the valid activities (camping, backpacking, winter camping, day hiking) where the schema has no enum and only says 'Activity whose PDF to return.' That enumeration is real added value for a required parameter.

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?

Names a specific verb and resource ('Get the STANDARD published Wilderness Times checklist as a ready-made PDF') and immediately bounds the scope to the unedited published list. It also enumerates the supported activities, letting an agent confirm eligibility 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?

Explicitly states the condition that selects the sibling: if the user has added, removed or filtered items, call share_checklist instead. It even explains what that alternative returns (a builder link with PDF/Excel/Sheets/print export), so routing is unambiguous.

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