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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered structurally; the description reinforces this with 'opens nothing by itself,' which meaningfully confirms no side effects occur. It does not describe the shape or length of the returned instructions, but for a zero-parameter read tool the added value is real albeit modest.

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 two operational sentences earn their place and the workflow is front-loaded, but 'from ChatGPT, Claude or any AI agent' is filler, and the closing paragraph about 404s on /api, /developers and /docs is verbose rationale that could be compressed to 'no public API; use browser tools.' The assessment of the missing-API evidence is longer than needed to justify the workflow.

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 guidance tool with no output schema, the description covers the essentials: what is returned, that no side effects occur, and how to act on the result. The absence of any detail on the granularity or format of the returned steps is a minor remaining gap, but nothing required for correct invocation 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?

The tool takes zero parameters and the schema is fully closed with additionalProperties false, so there is nothing parameter-level for the description to explain. The baseline for a no-parameter tool applies.

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 makes clear this is a guidance tool that returns step-by-step instructions ('screens, buttons, fields') for statement contact lines rather than performing the action, which distinguishes it from action-oriented siblings. The weakness is that 'Statement contact lines' is a bare noun fragment without a verb specifying whether it is viewing, editing, or configuring them, so the target resource is clearer than 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?

It explicitly routes the agent: read the steps here, then execute with the cotlet_browser_* tools in the Cloud Browser, and states the tool 'opens nothing by itself.' That is concrete when-to-use and what-happens-next guidance. It does not differentiate against other statement-related siblings such as statement_preview or statement_run, but the guidance it does give is actionable.

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