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

Annotations cover read-only/open-world safety, but the description adds the non-obvious paywall gating (Camp Map Pass, CA$55/yr or CA$5/mo) and the content boundary around regulations. It does not state rate limits or response shape, but against the annotation baseline this is a solid additive disclosure.

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 compact sentences with the gating requirement front-loaded before content and exclusions. The pricing detail ('CA$55 a year or CA$5 a month') is arguably surplus for tool selection but is plausibly user-facing context.

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 should say more about what comes back – the presence of check_spot/confirm_spot siblings suggests spots carry identifiers that flow into later calls, which is never explained. Gating and content scope are covered, so it is adequate but not complete for an agent's full workflow.

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 description contributes nothing about lat, lng, limit, or radius_km. Schema coverage is 75%, so lat/lng/radius_km carry their own docs, but 'limit' is undocumented in both places. With the schema doing most of the work, a baseline 3 is appropriate.

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 name and title say 'Hunting scouting picks', but the description never states the action verb or the return resource explicitly – it only describes content attributes (access points near 5-10 year old cut blocks and winter ranges, with hunting unit and trail-camera signal). An agent can infer it returns a list of spots, but no sibling (find_spots, check_spot, confirm_spot) is named to disambiguate.

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 gives a real precondition ('Camp Map Pass only') and an explicit scope exclusion (seasons/bag limits not included), which is useful context. However, there is no guidance on when to choose this over nearby siblings like find_spots or check_spot – usage is only implied.

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