get_exercises_by_equipment

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It does state that the tool returns a list of exercises and documents pagination behavior via limit and offset, which is useful. However, it does not mention read-only status, sorting, default ordering, error handling, or behavior when no exercises match, so the behavioral picture is only partially complete.

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?

The description is compact and well-structured: a one-sentence summary followed by a clear Args section and a Returns line. Every line contributes necessary information, with no filler or repetition of the schema's redundant title fields.

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?

All parameters are documented with defaults and examples, and an output schema exists so return structure is already defined. The only minor gap is not mentioning that valid equipment values could be obtained from the sibling list_equipment tool, and not specifying whether equipment matching is exact or substring-based, but overall the description is complete enough for correct invocation.

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%, but the description compensates fully: equipment gets concrete examples, limit gets its default and maximum, and offset gets its default. This adds real meaning beyond the bare schema definitions, so an agent knows exactly what values are expected.

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 opening line 'Get exercises that use specific equipment' precisely states the verb, resource, and filtering criterion. This clearly distinguishes the tool from siblings like get_exercises_by_body_part and get_exercises_by_target_muscle, and the equipment examples make the scope immediately understandable.

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 description makes the intended use obvious: call this when you need exercises filtered by equipment. It does not explicitly mention alternatives or exclusions, such as 'for keyword search use search_exercises', so it misses the full when-versus-alternatives guidance, but the context is clear enough for an agent to choose correctly.

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