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

readOnlyHint=true already declares the safety profile, so the bar is lower, but the description adds nothing: no pagination behavior, no indication of what an 'imported' sale is tied to (an import batch), and no hint about ordering or volume of results.

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?

One short, front-loaded sentence with no filler, but the brevity comes at the cost of substance rather than being earned economy.

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 paginated list tool with no output schema and two undocumented paging parameters, the definition leaves the agent without enough context to call it confidently or distinguish its results from the summary endpoint.

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 coverage is only 33% – organizationId is documented in-schema, but pageSize and pageNumber have no descriptions anywhere. The description contributes zero parameter meaning, so it fails to compensate for the low coverage.

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 restates the tool name rather than stating the operation: 'Historical sales imported for a gym' describes the data, not 'list'. It offers no differentiation from close siblings such as get_gym_imported_sales_summary, list_gym_imports, or list_gym_imported_members.

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 at all. The agent is not told whether this is the per-record listing versus the summary tool, nor that an organizationId must come from list_my_organizations (that hint lives only in the schema).

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