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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral context — that it returns procedural guidance rather than data and performs no action itself — but stays silent on result size, failure modes when no matching exercise exists, or what the guidance looks like.

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 essential constraint (returns instructions, opens nothing, use cotlet_browser_* next) is front-loaded in the second sentence. However, the closing fragment 'CoachingPortal's official API: CoachingPortal publishes no public API' is awkwardly phrased and partially redundant, and the opening ChatGPT/Claude/AI-agent clause spends words on marketing framing.

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?

No output schema exists, so the description does the work of explaining what comes back, which it does at a high level. The notable gap is that a 'search' tool with zero parameters never explains how the search subject is conveyed, leaving the agent unsure how to actually invoke it meaningfully.

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 the schema carries no semantics to undercut. The description adds the relevant constraint that the account searched is the user's own, though it never addresses how a search term would be supplied.

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?

Names a concrete verb and resource ('Search exercises') scoped to 'the user's own CoachingPortal account', which separates it from siblings like coachingportal_search_food_library by subject matter. It never explicitly contrasts itself with a sibling, so it stops short of a 5.

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?

Gives a clear workflow: this tool returns step-by-step instructions (screens, buttons, fields) and 'opens nothing by itself', after which the agent must act via cotlet_browser_* tools in the Cloud Browser. It states no explicit when-not-to-use condition or named alternative, so it is strong but not exhaustive.

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