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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered; the description still adds real value by stating 'opens nothing by itself', warning the agent that no action is performed server-side and that the follow-up must happen through the browser tools. The closing note about StreamElements' REST API and lack of an official MCP server is background trivia rather than behavior, which keeps this out of 5 territory.

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 message (returns step-by-step instructions, then act via cotlet_browser_*) is front-loaded, but the trailing sentence about the kappa v2 API, OAuth2 flow and a dated 'no official MCP server' check does not help an agent decide or invoke. That aside occupies roughly a third of the text and dilutes the operative guidance.

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 zero parameters, no output schema and read-only annotations, the description covers what the agent needs: what comes back (screens/buttons/fields walkthrough) and how to complete the task afterward. What is missing is preconditions such as whether the user must already be logged into the StreamElements Cloud Browser for the follow-up steps to work.

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 no parameters, so 4 is the baseline and there is no schema semantics for the description to compensate for. Nothing in the text misdescribes the (empty) input contract.

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 identifies the resource (chat commands in the user's own StreamElements account) but the stated behavior conflicts with the tool name: 'List chat commands' implies returning command data, while the body says it 'Returns how to do it in StreamElements step by step (screens, buttons, fields)'. An agent cannot tell from the name alone whether it receives a list of commands or a UI walkthrough, and the description never reconciles the two.

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?

Explicit sequencing is given: this tool 'opens nothing by itself; then do it with the cotlet_browser_* tools in the user's StreamElements Cloud Browser', which tells the agent to call this for the how-to and then hand off to the browser tools. There is no explicit when-not condition or mention of the sibling streamelements_edit_command, so it stops short of full routing guidance.

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