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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds non-obvious behavior beyond that: the tool returns procedural instructions rather than acting, and it explicitly opens nothing, which prevents an agent from assuming the profile was retrieved. The API-availability note is extra context but not a behavioral trait.

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 operative content (what it returns, that it opens nothing, and the cotlet_browser_* handoff) is front-loaded and well placed. The closing paragraph about gymdesk.com/api, /developers and docs subpaths returning 404 is verbose sourcing detail that consumes roughly a third of the text without helping an agent call the tool.

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, read-only helper with no output schema, the definition covers everything an agent needs: what comes back (screens, buttons, fields), the fact that no side effect occurs, and the follow-up tool family required to actually perform the action.

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?

There are zero parameters and full schema coverage, so baseline 4 applies. The description correctly implies no inputs are needed, and nothing is left ambiguous about argument shape.

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 states a specific verb and resource (view a member or visitor profile) and, unusually, clarifies the deliverable: a step-by-step how-to rather than the profile data itself. It is distinguishable from the many write-oriented siblings such as edit_member_profile, though it never names a sibling directly.

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 give the chaining rule that an agent must follow ('opens nothing by itself; then do it with the cotlet_browser_* tools'), which is real usage guidance. However, it never says when to pick this over the other read siblings (payment history, attendance reports, growth reporting), so the choice among read tools remains inferred.

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