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

Annotations already declare idempotentHint=true, destructiveHint=false, openWorldHint=true. The description earns credit beyond them by specifying the channel (SMS/push), the concrete idempotency contract for retries, and the side effect that available-now results can consume an alert credit. It still omits notification-delivery behavior and how existing alerts interact.

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 tight sentences, front-loaded with the action and the approval precondition, then the idempotency rule and the credit caveat. No filler, though the credit sentence is vague enough that it earns less than its space.

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 covers the approval gate, idempotency, and billing side effect. However, for a 7-parameter creation tool with three undocumented filter parameters, the guidance is not complete enough to call it confidently.

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 description coverage is 0% across 7 parameters including nested objects, so the description must carry the load. It names target, dates, partySize and idempotencyKey conceptually, but watchOptions, siteTypeFilter and excludedCampgroundSlugs go entirely unexplained in both schema and description.

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: creates an SMS/push availability alert, and names the key inputs (target, dates, party size) plus the idempotency contract. It does not explicitly contrast itself with siblings like list_alerts, stop_alert, or check_availability, but the action is unambiguous.

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 a real precondition (create only after the user approves target, dates and party size) and idempotency usage rules (new key per intended alert, reuse on retries). It never says when to prefer this over check_availability or enable_sms_alerts, so routing guidance is only partial.

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