Exercise Search

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

Annotations already provide readOnlyHint, idempotentHint, and openWorldHint. Description adds the open-source database origin and licensing (CC-BY-SA), which is useful but not critical. No contradiction, but minimal extra behavioral disclosure beyond annotations.

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?

Two sentences: first front-loads the action and key return fields, second adds source attribution. Every sentence is valuable; no wasted words.

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?

Given output schema exists, description need not detail return structure, yet it names the three fields (name, category, ID). Also mentions database scale (896 exercises) and licensing, providing sufficient context for a simple search tool.

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?

Only one parameter 'term' with 100% schema coverage, including examples. Tool description repeats some examples, adding no new semantic meaning. Meets baseline for high coverage but doesn't exceed.

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?

Description clearly states verb 'Search' and resource 'exercises by name', with explicit examples (bench press, squat). Distinguishes from sibling 'exercise_details' by indicating this tool returns summary info (name, category, ID) for further detail lookup.

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?

Description gives clear context for when to use this tool (searching exercises by name) and implies that after search, use exercise_details for more info. Lacks explicit 'when not to use' or alternatives, but the purpose is straightforward.

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