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

readOnlyHint=true already covers the safety profile. On top of that, the description discloses return content that has no output schema to carry it: the role, the exact capabilities granted, and the custom role's name. Useful behavioral context beyond the annotation.

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: what is returned first, then the usage directive. No filler, and the most decision-relevant content is front-loaded.

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 simple single-param read with no output schema, the description covers both the returned data (role, capabilities, custom role name) and the call-first usage pattern. Only the organizationId parameter's semantics are left unaddressed.

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?

Schema description coverage is 0% and the description never mentions organizationId or its expected format. The phrase "in a gym" implies org scoping, but the single required parameter is left to be inferred from its self-explanatory name. With no schema documentation, the description should compensate more than it does.

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?

States a specific verb+resource: retrieves the coach's own role in an organization plus the capabilities it grants. This is distinguishable from siblings like get_organization_role_guide (generic role docs) and get_organization_profile, though those siblings are not named. Clear but without explicit sibling differentiation.

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?

"Call this first to know which gym tools this coach may use" gives an explicit, actionable directive for when to reach for the tool. No when-not condition or named alternative is provided, which keeps it below a 5.

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