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

The annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered structurally. The description adds one meaningful piece of context beyond them: the effect is permanent, and it targets only public relay actions rather than the conversation entirely. It says nothing about recovery, permissions, or what happens to existing messages.

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 wasted words; the key qualifier 'Permanently' is placed where it will be read first. It is efficient, though its brevity is partly under-specification rather than tight editing.

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 destructive, irreversible mutation with three undocumented parameters and no output schema, one sentence is not enough to call it correctly or explain the result. The annotation coverage offsets some risk, but the parameter gaps and absent recovery/permission context leave the definition materially incomplete.

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 three parameters, including a 'reason' enum with five values and the pairing of conversationToken with conversationId, so the description needed to compensate and does not. It never mentions any parameter, leaving the meaning of the token/id pair and the purpose of the reason enum entirely undocumented.

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 a specific verb (block) and resource (conversation) and adds scope ('further public relay actions'), which is more precise than the title alone. It does not explicitly distinguish itself from close_conversation, the closest sibling, so an agent must infer the difference.

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 only implied: 'Permanently' hints that this is the irreversible counterpart to close_conversation and reopen_conversation, but no sibling is named and no condition for choosing one over the other is given. There is also no guidance on when not to use it.

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