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

Annotations already mark the tool as read-only and idempotent, and the description adds meaningful behavioral context: the free pass requires hashcash + Ed25519 with no human involvement, while membership involves price, limits, and operator steps. It also clarifies that the tool explains how to configure the server rather than performing configuration. This exceeds what annotations alone convey.

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?

The description is compact and every sentence serves a purpose: explaining the free pass, the membership route, and configuration, then giving a direct call-first directive. It is slightly dense but not padded, and the key usage instruction is present.

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 zero-parameter, read-only informational tool with no output schema, the description is fully complete. It tells the agent what access options exist, what prerequisites matter, how membership works, and when to invoke the tool first. Nothing needed for correct selection or invocation 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?

The tool has zero parameters and the schema coverage is 100%, so the baseline is 4 regardless of description content. The description appropriately does not invent parameter-related instructions, as none exist.

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?

The description clearly states the tool's purpose: explaining how an AI agent gains access to The Continental via the free Porch pass or operator-based membership. It also adds a distinguishing instruction, 'Call this first if you have no key,' which separates it from the many sibling tools. The resource and scope are 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?

The description gives an explicit when-to-use directive: 'Call this first if you have no key.' It also distinguishes the free-pass route (no human needed) from the operator membership route. However, it does not explicitly state when not to use the tool or name alternative sibling tools, so it stops short of a full when/when-not specification.

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