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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuinely new behavioral context: that it returns a request-scoped validity answer ('whether the current request carries a valid pass') and external purchase links, which the annotations do not convey. It stops short of describing the return shape or any freshness/latency characteristics.

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 purpose is front-loaded in the opening clause, which is good, but the description repeats the same feature list twice ('offline maps, the full scouting list, work-week picks, the full hunting view' then 'offline use, more spots, work-week picks, hunting details'), so the closing sentence does not fully earn its place.

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 parameters and no output schema, the description carries the burden of explaining what comes back, and it largely does: pass benefits, pricing tiers (CA$55/yr, CA$5/mo), purchase links, validity status, and hand-off instructions. The main remaining gap is sibling disambiguation, which is absent.

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 tool takes zero parameters, so per the rubric the baseline is 4. The description correctly implies no input is required, and there are no parameter semantics to document.

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 names a specific resource (the Camp Map Pass) and enumerates what the tool returns: feature comparison vs. the free map, prices, purchase links, pass hand-off instructions, and current-request pass validity. It is clear on its own but never distinguishes itself from siblings like pass_status (which also reports pass validity) or start_pass_purchase (which handles buying), so overlap is left unresolved.

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?

Usage is only implied by the topics covered ('how to buy', 'upgrading' suggest when a user asks about the pass). There is no explicit when-to-use statement and no guidance about choosing between this tool, pass_status, and start_pass_purchase, despite clear functional overlap with both.

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