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

Discloses the single most important behavioral trait an agent could get wrong here: the tool 'opens nothing by itself' and only returns step-by-step instructions (screens, buttons, fields). It also explains the reason — 'CoachingPortal publishes no public API' — which tells the agent why browser automation is required. All of this is consistent with readOnlyHint=true, idempotentHint=true, destructiveHint=false.

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?

Three short sentences with the key constraint — that it opens nothing — front-loaded and emphasized. Minor filler remains: 'from ChatGPT, Claude or any AI agent' adds no decision-relevant information, and the closing sentence is awkwardly phrased with the 'official API: publishes no public API' redundancy.

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, no-output-schema guidance tool, the description covers everything needed: what it returns (step-by-step screens, buttons, fields), what it does not do (opens nothing), and what the agent must do next (cotlet_browser_* tools). Nothing an agent needs in order to call it correctly 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, so there is nothing for the description to disambiguate; the baseline of 4 applies. The description correctly implies no argument is needed to identify the leaderboard because it operates on 'the user's own account'.

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 ('Refresh leaderboard') scoped to 'the user's own CoachingPortal account', and critically clarifies that the tool returns instructions rather than performing the refresh. It does not name a sibling such as coachingportal_create_leaderboard, so sibling differentiation is implicit rather than explicit.

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?

Explicitly routes the agent onward: 'then do it with the cotlet_browser_* tools in the user's CoachingPortal Cloud Browser' tells the agent exactly what to do after this call. It stops short of stating when NOT to use it (e.g. when a direct API-backed sibling should be used instead), but the handoff condition is unambiguous.

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