fitbit_get_exercises

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

With no annotations, the description carries full burden. It discloses cache behavior, live fetch option, and an important reliability note about HR data from cycling. Returns fields are listed. Could mention rate limits or auth, but sufficient for core transparency.

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?

Description is concise with clear sections for args and notes. Every sentence adds value; no redundancy. Well-structured for quick scanning.

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 the tool's complexity (caching, live fetch, filtering) and presence of output schema, the description covers essential aspects. Could explicitly state that cache requires prior sync, but overall complete enough for an agent to use correctly.

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?

Input schema has zero description coverage, but the description fully documents all four parameters: date formats, defaults, filtering semantics for exercise_type, and boolean live. Adds substantial meaning beyond the schema's minimal titles.

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 description clearly states 'Get exercise log entries (individual tracked activities).' It specifies the resource and action, distinguishing it from sibling tools like fitbit_get_activity by focusing on exercise logs. The mention of default cache vs live adds further specificity.

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?

Provides explicit guidance: default cache usage, live=True for API fetch, prerequisite to run fitbit_sync, and filtering by exercise_type. Lacks explicit when-not-to-use scenarios, but covers key usage contexts.

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