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

Annotations already supply destructiveHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is covered structurally. The description still adds meaningful context beyond them: it discloses the blast radius (files created by the chat survive) and that the removal propagates to the muse.ai app, i.e. this is not a soft/hidden delete. It stops short of saying whether deletion is reversible or what permissions are required.

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?

Three short, front-loaded sentences with zero filler: what it deletes, what survives, and the underlying endpoint. Every sentence contributes information an agent can act on.

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 single-parameter destructive tool with full annotation coverage and no output schema, the definition covers the essentials: the target, the persistence of derived files, and the external visibility of the delete. Nothing an agent needs in order to invoke it correctly 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% for the single chatId parameter, so the structured field already carries the naming burden. The description's 'DELETE /chats/{chatId}' reinforces how chatId is bound into the path but adds no format, source, or lookup guidance beyond the schema. Baseline 3 is appropriate when the schema does the heavy lifting.

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 pairs a specific verb (Delete) with a specific resource (Muse chat) and further disambiguates it from the sibling delete tools (delete_asset, delete_file, delete_permission_rule) by naming the target object explicitly. It also states the visible consequence (it disappears from the muse.ai app), which confirms the effect of the operation.

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?

There is no when-to-use or when-not-to-use guidance, and no routing to alternatives such as muse_cancel_chat, which is the obvious sibling for stopping a chat without destroying it. The clarification 'the files it made stay' is a side-effect note, not usage guidance, so the agent must infer the selection criteria on its own.

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