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

With readOnlyHint and destructiveHint=false already declared, the description adds the crucial context that the tool 'opens nothing by itself' and merely returns screens/buttons/fields instructions — this resolves the apparent conflict between the 'remove' name and the non-destructive annotations. It stops short of describing the instruction payload's shape or any failure modes, which keeps it at 4 rather than 5.

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 behavior is buried in a long second sentence, while the closing sentence about StreamElements's kappa v2 REST API and 'no official MCP server (checked 17 Oct 2026)' is largely irrelevant to selecting or calling this tool. Readable, but not front-loaded and carrying 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 no-parameter, read-only guide tool with no output schema, the description supplies what an agent needs: it does not perform the removal, it returns step-by-step instructions, and the actual action is delegated to cotlet_browser_*. Only the granularity/format of the returned steps is left unstated.

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?

The tool takes zero parameters and the schema coverage is 100%, so there is nothing for the description to disambiguate. Baseline 4 applies; no parameter claims in the description conflict with the empty 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?

The first sentence frames the tool as 'Remove song request in the user's own StreamElements account,' which reads like a mutation, and only the second sentence reveals that it actually returns step-by-step instructions and opens nothing itself. The real purpose (a how-to guide tool) is stated but back-loaded, so an agent skimming the opener could misidentify it.

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 does tell the agent what happens next ('then do it with the cotlet_browser_* tools in the user's StreamElements Cloud Browser'), which is a useful workflow hand-off. But there is no explicit when-not-to-use guidance and no naming of which specific browser sibling (open, navigate, click) to start with, leaving the sequencing to inference.

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