get_progress

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

No annotations exist; the description only states it returns data but lacks details on auth requirements, error handling, or output format, leaving the agent with minimal behavioral context.

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?

Single sentence, no fluff, but could be slightly more informative without losing conciseness. Loses a point for being too minimal.

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?

Missing key context like whether progress is for a single exercise or all, the exact nature of 'coaching signals,' and how the output relates to the input parameter, despite having an output schema.

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?

The only parameter 'exercise' has no description in schema and the tool description does not explicitly state that progress is per exercise; it only implies through examples. With 0% schema coverage, the description should compensate but does not.

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 'Return coaching signals' with specific examples (1RM, volume trend, PRs), and the verb+resource is distinct from sibling tools like get_exercise_history or get_current_workout.

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?

Implies usage when progress data is needed, but no explicit guidelines on when to use this vs. siblings or when not to use it.

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