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

Annotations already mark this read-only, idempotent, non-destructive and closed-world, and the description is consistent with that. It adds genuine context beyond the annotations: it opens nothing itself, it returns instructional content rather than performing a change, and there is no public API to fall back on. The return shape is described only loosely, which keeps it from a 5.

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 message (returns steps, does not act, then use the browser tools) is front-loaded and useful. However, the closing line "CoachingPortal's official API: CoachingPortal publishes no public API" is awkwardly worded and repetitive, and "CoachingPortal" is restated four times in three sentences, adding noise.

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 output schema, the description carries the burden of explaining what comes back, and it does so at a high level (screens, buttons, fields). The handoff to cotlet_browser_* tools makes the overall flow actionable. A little more on what the step-by-step output contains, or on error cases such as a client who already exists, would make it complete.

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. The description correctly implies no input is needed beyond the user's own account context, and there is no schema-level parameter detail to compensate for.

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 gives a specific verb and resource ("Invite client in the user's own CoachingPortal account") and states the output form (step-by-step screens, buttons, fields). It also makes clear the tool does not perform the action, which separates it from execution tools. It does not directly contrast with the sibling coachingportal_invite_coach, so it falls 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?

It states the workflow clearly: get the steps here, then execute with the cotlet_browser_* tools in the user's CoachingPortal Cloud Browser. The "no public API" note explains why the browser route is required. It lacks an explicit when-not-to-use clause (e.g. what to do if the client already has a pending invite, handled by coachingportal_remove_client_invitation or similar).

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