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

Beyond the destructiveHint/readOnlyHint annotations, the description discloses what is destroyed (MUC room, archive, affiliations), irreversibility, the configuration gate, authentication mode, and exact 401/403/404 failure semantics. This is rich behavioral context that annotations alone do not provide.

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 dense but every sentence carries operational value: effect, permanence, gate, auth, and errors. The most important fact (permanent deletion) is front-loaded, and there is no filler.

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 two-parameter tool with no output schema, the description covers the outcome, prerequisites, configuration requirement, and all likely failure modes. Nothing essential for an agent to call it safely 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?

Schema description coverage is 100%, and the schema already documents appId's default behavior and chatJid's format and source tools. The description adds no parameter-specific detail beyond the schema, so the baseline of 3 applies.

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 states a specific verb and resource: 'Permanently delete a chat room from an app the caller owns' and details the exact scope (removes MUC room, message archive, member affiliations). This clearly separates it from sibling tools like ethora-app-delete (app-level deletion) and ethora-app-create-chat (creation).

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?

It gives clear invocation context: user-auth mode with an active session, app ownership, and the ETHORA_MCP_ENABLE_DANGEROUS_TOOLS=true gate. It does not explicitly name alternatives or state when not to use it, but the prerequisites and error conditions effectively guide selection.

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