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

The annotations already declare destructiveHint=true and readOnlyHint=false, but the description goes well beyond them by detailing what gets removed (chat rooms, files, indexed RAG sources, bot config), immediate user sign-out, irreversibility, the environment variable gate, and error conditions. This is rich behavioral context with no contradiction.

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?

Dense but well organized: primary effect and consequences first, then safety gate, auth requirements, error semantics, and a related alternative. Every sentence adds operational value without padding.

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 single-parameter tool, the description covers what the action does, what it destroys, who may call it, what can go wrong, and what safer alternative exists. Nothing essential is missing for an agent to invoke it correctly.

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 coverage is 100% and the appId parameter is already well documented with its format and how to obtain it. The description adds ownership and 404 context but does not substantially extend parameter meaning beyond the schema.

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?

States a specific verb and resource ('permanently delete an Ethora app the caller owns') and lists concrete consequences. It clearly distinguishes itself from related operations like ethora-app-delete-chat and ethora-app-update.

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?

Explicitly says the caller must own the app, requires user-auth active session, and names the safety gate ETHORA_MCP_ENABLE_DANGEROUS_TOOLS=true. It also points to an alternative for deactivating the bot via ethora-app-update with botStatus: 'off'.

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