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 genuinely useful context beyond that: sort order and that amounts are in the smallest currency unit (avoiding a unit misinterpretation). It says nothing about pagination behavior or who may call it.

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 short sentences with zero filler, and the scope constraint is front-loaded. Every sentence earns its place.

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 paginated list with no output schema, the description covers what the list contains, its ordering, and currency units. It omits pagination semantics and any indication of scope/permission requirements, so it is adequate but not fully self-sufficient.

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 adds nothing about any of the three parameters. organizationId, pageSize (max 100, default 50), and pageNumber (default 1) are documented only by JSON Schema types and defaults; the 'newest first' ordering does not tell the agent how to page.

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 ('Payments received across the gym') with an explicit scope ('all coaches') and an ordering guarantee ('newest first'). It implicitly separates itself from get_organization_earnings and billing_summary, but never names them, so the differentiation is by scope only.

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?

No when-to-use guidance and no named alternatives, despite several plausible siblings (get_organization_earnings, billing_summary, list_subscriptions). The agent must infer that this is the raw transaction list rather than a summary.

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