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

Goes well beyond the readOnly/openWorld annotations by disclosing pagination via offset, per-call plan caps with concrete numbers (Free 10, Starter 100, others 200), and the exemption from the distinct-exercise media limit — quota behavior an agent otherwise could not anticipate. It stops short of describing the response envelope or what happens when offset exceeds the result set.

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?

Three tight sentences, front-loaded with the payload and purpose, then the quota exemption, then paging and limits. No filler and every clause carries operational 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 10 parameters, no output schema, and only 50% schema coverage, the description supplies the essential export semantics, quota behavior, and paging model an agent needs to call it correctly. Remaining gaps are the undocumented filter and language parameters, which are minor but real for a tool with this many options.

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 50%, yet the description only clarifies offset (paging) and format (JSON/CSV), plus loosely maps fields to the exported columns. It says nothing about the filter parameters target, bodyPart, equipment, or the lang parameter, so it does not fully compensate for the schema's gaps.

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 concrete verb and resource plus scope: exports exercise ids/names/muscles/equipment without media, as JSON or CSV, for seeding databases or fixtures. It also explicitly separates itself from media-oriented siblings by noting it does not consume the distinct-exercise media limit.

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 seeding/fixtures use case gives clear context for when to reach for this tool rather than get_exercise or search_exercises, and the mention of the media limit reinforces that. It does not name an alternative outright or state a when-not condition, so routing is still partly inferred.

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