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

readOnlyHint=true already tells the agent this is a safe read. The description adds useful scope context by framing the content as public-facing profile plus settings, but it does not disclose whether the caller must be a member/admin of the org, whether any fields can be null, or anything about access restrictions.

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 sentences, front-loaded with the payload description and then the id-routing hint. The field enumeration is dense but each item conveys distinct return content, and there is no filler.

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 return-value burden and does so by listing the fields returned, which is the key information an agent needs. Combined with readOnlyHint covering safety, the only real gap is access/prerequisite context.

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 is one parameter (organizationId) with 0% schema description coverage, so the schema alone leaves its origin ambiguous. The description partially compensates by pointing to list_my_organizations as the source of the id, but does not clarify the expected format or whether it must be an org the caller belongs to.

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 (a gym's public-facing profile and settings) and enumerates the specific fields returned (description, contact, city, slug/visibility, branding, community switch, AI guidelines, payout mode), which lets an agent distinguish it from siblings like get_organization_dashboard or get_organization_access. It stops short of explicitly contrasting with update_organization_profile, so it is clear but not fully sibling-differentiated.

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 provides one concrete routing hint — 'Use list_my_organizations for the id' — which tells the agent how to obtain the required parameter. However, it gives no guidance on when to prefer this tool over the other organization-read siblings (dashboard, access, earnings), leaving selection largely implied.

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