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 content context — that results carry created/skipped/failed tallies per import — but says nothing about pagination, ordering, time ranges, or whether all historical imports or a subset are returned.

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 sentence, front-loaded with the resource and scoped parenthetically, with zero filler. Nothing could be removed without losing 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?

For a read-only, single-parameter listing with full schema coverage and no output schema, the description covers what the tool is and what the results summarize. It stops short of covering result ordering/pagination or the relationship to the import-lifecycle siblings, which is the only remaining gap.

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?

The single parameter is fully documented in the schema (100% coverage, with a pointer to list_my_organizations), so baseline 3 applies. The description adds no semantics beyond what the schema already provides.

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 the resource precisely — past data imports for a gym — and enumerates the covered domains (leads, members, sales) plus the returned counts (created/skipped/failed), which separates it from sibling listers like list_gym_imported_members or list_gym_imported_sales. The verb is only implicit ('past data imports'), and no sibling is named as an alternative.

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 call this versus the adjacent tools (get_gym_imported_sales_summary, list_gym_coach_import_batches, list_gym_imported_members/sales, undo_gym_import, commit_gym_import). An agent has to infer from the description alone that this is a history/audit listing rather than a per-record listing.

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