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

Annotations already declare readOnlyHint=true, so the safe-read profile is covered. The description adds that results include 'audience and reach', a useful hint about returned content beyond the annotation, but it discloses nothing about pagination, limits, or ordering. Against annotations that carry the safety burden, this is adequate but thin.

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?

A single short sentence with no filler, and the resource is front-loaded. It is grammatically a noun fragment rather than a full statement of action, which slightly weakens structure but not economy. Nothing in the sentence is redundant.

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 one-parameter read tool with no output schema, the description is close to sufficient and even sketches the return fields (audience, reach). It omits pagination/limit behavior and any tie between the org scope and the required parameter. Adequate but with clear gaps.

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, so the description must compensate and does not. It never mentions organizationId or that it is required, only loosely implying org scoping via "a gym's". The agent gets no format or sourcing detail for the sole input.

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 specific resource (announcements sent to a gym's coaches and/or clients) and its qualifier (previously sent), which is enough to distinguish it from the sibling send_organization_announcement by tense alone. It lacks an explicit verb like 'list' or 'retrieve', so the read action is only implied rather than stated. Purpose is clear but not crisply verb-led.

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?

There is no guidance on when to use this tool versus alternatives such as get_organization_dashboard or send_organization_announcement, and no stated prerequisites or exclusions. The 'previously sent' phrasing hints at historical retrieval, but usage is left entirely to inference. No when-to-use or when-not-to-use information is provided.

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