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

Annotations already declare destructive=true, idempotent=true, and readOnly=false, so the safety profile is covered. The description adds non-obvious behavioral context beyond the annotations: the per-account browser cap of 2, the Queued status for waiting browsers, and the irreversibility of the chat-deletion ordering. It could say more about what state is lost when a browser is stopped.

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 core action is front-loaded in the first sentence and the constraint/ordering caveats follow compactly. The raw endpoint string at the end adds little for an agent that will call the tool by name, but nothing is padded or redundant.

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?

With no output schema and only two required params, the agent needs mainly lifecycle and ordering context, which the description supplies (concurrency cap, queued state, stop-before-delete rule). Return/confirmation behavior is not addressed, a minor gap for a destructive operation.

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 both required parameters, so the schema already documents chatId and taskId. The description embeds both in the endpoint path but adds no format or sourcing guidance, making the baseline 3 appropriate.

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 ('Close a browser the agent opened') and even names the HTTP endpoint, so the action is unambiguous. It does not, however, distinguish itself from the sibling tool muse_release_browser, which an agent may reasonably confuse with this one.

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?

Gives explicit when-to-use context (stop one that is no longer needed), explains the concurrency constraint that motivates it (max 2 browsers, new ones queue), and states a hard ordering rule: always stop before deleting the chat, because a deleted chat's browser becomes unreachable.

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