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

Annotations already carry the safety profile (readOnly, idempotent, non-destructive, not open-world), so the bar is lower. The description adds genuine behavioral context by disclosing that a permit is informational rather than a purchasable cart item. It omits ordering/permission details, but with annotations covering safety this is solid.

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?

A single dense topic sentence plus a short clarifying exclusion; no filler. The opening is a topic list rather than a front-loaded statement of what the tool does, which slightly blunts the lead.

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 an output schema present, the description needn't document return values, and annotations cover safety. The topical enumeration sets expectations adequately for a zero-parameter lookup, leaving little an agent still needs to know.

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 the schema has nothing for the description to compensate for — baseline 4 applies. Nothing in the text misrepresents the parameterless nature of the call.

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?

Enumerates exactly the permit facts it returns (where needed, issuer, cost, max stay, processing time, sites, application location), which makes its resource clear. It also distinguishes itself from the cart-building siblings by stating 'The permit is not a line in the cart.' No explicit verb, but the scope 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?

Usage is implied: consult this when a guest asks about camping permits. The only stated boundary is the negative 'not a line in the cart,' which steers away from build_cart_link but doesn't say when or when not to call it versus check_availability or get_product.

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