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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds the non-obvious and important fact that it 'opens nothing by itself' and returns instructions rather than results, which an agent could not infer from the annotations. It does not describe the shape of the returned steps or any account/permission prerequisites.

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 and the handoff to browser tools are front-loaded and useful. However, 'from ChatGPT, Claude or any AI agent' is filler, and the trailing 'Sleeper has only a limited API (checked 28 Oct 2026)' is a dated maintenance note that does not help an agent invoke the tool.

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 zero-parameter, read-only tool with no output schema, the description covers what it returns, what it does not do, and what to do next. The one remaining gap is the structure or granularity of the returned step list, which an agent may need in order to parse it.

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, so the baseline is 4 and there is nothing for the description to disambiguate. It correctly implies the tool is scoped implicitly to the authenticated user's own Sleeper account, which is the only scoping question that matters here.

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 names a specific resource (free agents) and then, crucially, clarifies what the tool actually returns: step-by-step instructions with 'screens, buttons, fields' rather than a data listing. That distinction is what an agent needs. The opening phrasing 'List free agents ... from ChatGPT, Claude or any AI agent' is awkward and could momentarily suggest the tool performs the listing itself, but the second sentence corrects that.

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 gives an explicit follow-up path: use the cotlet_browser_* tools in the user's Sleeper Cloud Browser to actually perform the steps. It also explains the reason — Sleeper's API is limited — which justifies why a procedural guide exists at all. It stops short of naming when NOT to use it or comparing against specific sibling tools.

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