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

readOnlyHint=true already covers the safety profile, so the bar is lower, and the description adds real value on top: it declares the content domains returned and explicitly excludes bank details. That exclusion is a meaningful behavioral constraint given the sibling update_my_bank exists. It does not cover any failure modes or rate/auth behavior, so it falls short of 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?

Two tight sentences, with the scope ("the coach's own full profile") front-loaded and the content enumeration following immediately. The bank-exclusion caveat is placed last as a qualifier, and no sentence is redundant with the name or title.

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?

There is no output schema, so the description carries the burden of describing return content, and it does so by naming the major field groups. Combined with the readOnly annotation and the zero-parameter schema, an agent has everything needed to call it correctly.

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, which is the baseline-4 case: there is nothing for the description to document beyond what the schema already shows. No parameter syntax, filtering, or format guidance is needed or missing.

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 uses a clear verb+resource ("The coach's own full profile") and enumerates the returned domains: contact info, professional info, availability, and transformations/testimonials. The phrase "coach's own" usefully separates it from sibling get_client_profile and get_organization_profile, though it does not distinguish itself from whoami, which likely overlaps.

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?

Usage is only implied: an agent infers it should call this when it needs the authenticated coach's profile. There is no explicit when-to-use guidance, no statement of when to prefer whoami or get_client_profile instead, and no prerequisites or auth notes beyond the annotation.

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