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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds genuine value on top: it discloses that results are role-scoped and that fields the coach's role cannot see are returned as null, which an agent cannot infer from the schema.

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 dense sentences with no filler, and the core scope statement is front-loaded before the null-behavior caveat. Every clause carries information.

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 properly carries the return-value burden by enumerating the fields returned. It falls short only on the parameter and on sibling disambiguation, but the data-shape coverage is strong for a one-param read tool.

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 required parameter (organizationId) with 0% schema description coverage, and the description never mentions it, its format, or that it identifies the gym being viewed. The description fails to compensate for the total lack of schema documentation.

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 clear verb+resource ('gym overview') and enumerates the exact data returned (client/coach counts, revenue, leads, classes, announcements, billing). However, it never distinguishes itself from the overlapping sibling get_organization_dashboard, leaving the agent to guess which overview to pick.

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?

The description implies a dashboard-style read but gives no when-to-use guidance, no conditions selecting it over get_organization_dashboard or get_organization_earnings, and no prerequisites. The role-scoping clause is the only contextual cue.

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