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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description reinforces this with the strong statement 'opens nothing by itself', so an agent won't expect a side effect. It goes further by explaining the two-step pattern (get steps, then drive the Cloud Browser with cotlet_browser_* tools) and noting no public API exists, which is context annotations cannot carry. It doesn't describe the shape of the returned steps, so not 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?

Three compact sentences, front-loaded with what the tool returns and immediately followed by the crucial 'opens nothing by itself' caveat and the required follow-up tooling. The trailing 'CoachingPortal's official API: CoachingPortal publishes no public API.' is slightly redundant wording that could be tightened to a single clause.

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 instruction tool with read-only annotations, the description covers what it returns, what it does not do, and what the caller must do next. The only gap is the lack of any note on what the step-by-step content covers (e.g., whether it is account-specific or generic).

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 and the baseline 4 applies. The description correctly signals no input is required by framing the output as generic guidance.

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 names the resource (coach invitation) and clarifies the actual behavior: it returns step-by-step CoachingPortal screens/buttons/fields rather than executing anything. The vague verb 'manage' in the name is disambiguated by 'Returns how to do it ... step by step', though it never distinguishes itself from the sibling coachingportal_invite_coach, leaving an agent to guess which one performs the invite.

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 gives a usable workflow — call this to get instructions, then act via the cotlet_browser_* tools in the user's CoachingPortal Cloud Browser — which is real when-to-use context. It stops short of explicit alternatives or exclusions (e.g., when to use coachingportal_invite_coach instead), so the agent must infer sibling selection.

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