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

With no annotations, the description carries the full load and does disclose real behavior: admit invites the knocker who must still accept the charter, decline sends a short note and permits re-knocking after 24 hours. It also states the auth model (OAuth or Bearer header, never as arguments), which is valuable operational context, though idempotency and knock-record lifecycle are unstated.

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 paragraph that front-loads the permission scope and the action semantics before the auth note. The auth sentence is somewhat tangential to the tool's purpose but remains compact and useful.

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 5-param, no-annotation, no-output-schema mutation tool, the description covers the action and auth dimensions but leaves role and expiresAt unexplained. It is adequate but not complete for an agent to call it without ambiguity.

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 only 20% (only 'space' is documented), so the description must compensate. It valuable-explains the action enum's effects, but role (member/guest, default member), knockId, and expiresAt are left with no meaning in either place.

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 names the two possible responses (admit/decline) and their effects, making it clear this tool resolves a pending knock request. 'Lead only' scopes who may call it. It does not, however, explicitly contrast itself with nearby siblings like knockout_on_space or accept_space_charter.

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 'Lead only' qualifier and the semantics of admit vs decline give implied usage context, and mentioning the charter links to the accept flow. There is no explicit when-not guidance or named alternative tool, so an agent must infer the routing.

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