highlight_body_regions

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

Discloses that highlighting replaces previous set, invalid IDs are silently dropped, and returns confirmation. No annotations needed as description covers all relevant behaviors.

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?

Every sentence adds value. Front-loaded purpose and behavior, then parameters. No fluff, well-organized.

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 simple tool with two parameters and output schema, description covers purpose, usage, behavior, parameter details, and return value. References sibling tools appropriately.

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?

With 0% schema coverage, description fully explains both parameters: regions (list of IDs, discovery via list_body_regions, invalid IDs dropped) and reason (caption shown to athlete). Adds meaning beyond schema defaults and types.

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?

Clearly states it highlights body regions in the dashboard's Body panel, with specific use cases and distinction from siblings like clear_body_highlights and list_body_regions.

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?

Explicitly describes when to use (draw attention, suggest pain source, visualize kinematic chain) and how to clear (empty list or sibling tool). No ambiguity.

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