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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the description's added value is the warning that a guessed integer silently selects the wrong option, plus the concrete ID-format example. It does not discuss auth or pagination, but for a read-only lookup that is a minor gap.

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 short, front-loaded blocks: what it returns, when to call it and why it matters, then the length-bracket rule. Every sentence carries information the agent cannot get from annotations or 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?

An output schema exists so return values need no explanation, and the description still covers the ID semantics and the bracket interpretation rule that the output schema alone would not convey well. Nothing needed to call this correctly is missing.

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% and both parameters (park_id, provider) are already documented in the schema, including the fact that provider is resolved from the park. The description adds no parameter syntax or precedence detail of its own, 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 ('the equipment vocabulary an alert can filter on, for the park's provider') and describes the exact entry shape (sub_equipment_id, name, kind). An agent knows precisely what this returns and that it is the vocabulary source for an alert filter, distinguishing it from every alert/itinerary 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?

Gives an explicit trigger ('Call this whenever the user describes what they are camping IN — a tent, a van, a 30-foot trailer') plus the consequence of skipping it ('You cannot set the equipment filter without it, and guessing the integer sets the wrong one silently'). No sibling actually competes here, so naming an alternative is unnecessary.

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