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

Annotations already establish readOnlyHint, idempotentHint, destructiveHint=false, and closed-world scope, so the safety profile is covered structurally. The description adds topical scope — that the policy covers pricing, what the price buys, refunds, and a signing scheme — which is genuine context beyond the annotations. It does not, however, say whether this is static reference text, its length, or whether the policy can change, leaving the return behavior implicit.

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 front-loaded sentence with no filler or repetition. The colon-delimited topic list is dense and scannable, though a few items ("the knock", "the trials") are evocative rather than informative, spending words on flavor instead of what the caller gets back.

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?

Complexity is low (no params, no output schema, annotations present), so the description does not need much. Still, with no output schema the description is the only signal about what is returned, and it only enumerates subject areas without saying the tool yields a policy document. The absence of any routing hint versus `how_to_enter` leaves a real gap.

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 there is no per-argument semantics for the description to contribute. Baseline 4 applies; nothing is missing on this dimension.

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?

"How to get in" plus a topic list (knock, proof-of-work, trials, price, house rules, refunds, signing scheme) gives a rough sense that this is the venue's admission policy, but there is no explicit verb stating that it retrieves/reports policy content rather than performing an action. It also fails to distinguish itself from the sibling tool `how_to_enter`, which reads as overlapping in subject matter. Purpose is inferable but vague rather than specific.

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?

There is no when-to-use guidance, no prerequisites, and no exclusion criteria. The agent is left to guess whether to call `door_policy`, `how_to_enter`, or `about` for admission-related questions, since the description never names or defers to an alternative despite clear sibling overlap.

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