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

Annotations only declare the write/open-world/non-idempotent profile, while the description adds genuinely non-derivable behavior: it requires the user's Camp Map Pass key, it shares a daily cap of 10 stored reports, and the data is consumed by the next scouting-list build. It stops short of explaining what happens on a repeat submission despite idempotentHint=false.

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?

Two dense sentences, front-loaded with the core action and followed by the key operational constraints; almost every clause (credentials, rate cap, downstream consumer) earns its place. The parenthetical enum list is slightly redundant with the schema.

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 mutation tool with no output schema, the description covers credentials, rate limiting, and downstream effect, which is most of what an agent needs. Missing only edge behavior on duplicate writes (consistent with idempotentHint=false) and failure handling.

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 75%, with lat/lng and name already documented in-schema. The description's recital of the outcome values duplicates the enum already present in the schema and adds no format or selection guidance beyond it, so the baseline 3 applies.

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?

States a specific verb and resource ('Stores what the user found at a camping spot') and enumerates the discrete outcomes, so an agent knows exactly what is being recorded. It does not explicitly distinguish itself from near-siblings like check_spot or report_conditions, which keeps it short of a 5.

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 context is implied by 'read by the next scouting-list build' and the pass-key requirement, which tells the agent when the write is meaningful and what credential is needed. However, there is no explicit when-to-use vs check_spot/report_conditions guidance or any stated exclusion.

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