wger_exercises

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

No annotations are provided, so the description carries the full burden. It states the tool reads from a workout database (implying read-only), but says nothing about pagination behavior beyond the default limit, rate limits, or whether results include full exercise details vs. summaries.

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 efficient sentence with the purpose front-loaded. No wasted words, though it is arguably too sparse given the tool's search/browse complexity.

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 search/browse tool with three parameters, no annotations, and no output schema, the description is too thin. It omits result structure, pagination behavior, and how the search/category parameters interact, leaving the agent to infer behavior.

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 100%, with all three parameters documented (limit, search, category) including a cross-reference to wger_categories for the category ID. The description adds no parameter detail beyond what the schema already provides, so baseline 3 is appropriate.

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?

Clear verb ('Search and browse') and resource ('exercises from the wger workout database'). The sibling set includes wger_categories and wger_muscles, and this tool is distinguishable by the 'exercises' resource, though the description never explicitly names those siblings.

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 guidance on when to use this tool versus wger_categories or wger_muscles, nor on how to combine them. The schema mentions wger_categories for category IDs, but the description itself provides no routing or usage context.

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