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

Beyond the annotations, the description adds crucial behavior: it 'opens nothing by itself' and returns instructions rather than performing the action, which explains why readOnlyHint/openWorldHint are false. It also discloses the justification (no public TrueCoach API, verified 11 Oct 2026), though it doesn't describe the shape or length of the returned guide.

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 critical fact (it returns a guide, not clients) sits in the middle of sentence two, behind an opening sentence padded with 'from ChatGPT, Claude or any AI agent'. The API-availability note is useful but formatted awkwardly with a stray colon and a verification date.

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 no parameters, no output schema and read-only annotations, the description covers what an agent needs: what it returns, that it has no side effects, and which tools to chain next. Missing only detail on the granularity/format of the returned steps, which is minor for a zero-arg lookup.

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?

Zero parameters, so there is nothing to disambiguate and the baseline applies. The description correctly implies nothing is needed from the caller beyond the account context.

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 headline verb+resource ('List clients in TrueCoach') suggests it returns client data, but the second sentence reveals the actual function: returning a step-by-step guide (screens, buttons, fields). That true purpose is disclosed but buried after a marketing-flavoured opening sentence, so an agent skimming could mis-select it expecting an actual client list.

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 does prescribe the follow-up path ('then do it with the cotlet_browser_* tools in the user's TrueCoach Cloud Browser'), which is genuinely actionable guidance. However it gives no when-not-to-use conditions and never distinguishes itself from siblings like truecoach_read_workout_results or cotlet_app_guide, which an agent would need to choose correctly.

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