get_workout

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

No annotations are provided, so the description carries the full burden. It only states 'Show the steps' without disclosing side effects, authentication needs, rate limits, or any behavioral traits beyond a simple read operation. The presence of an output schema is not mentioned nor is its content summarized.

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 consists of one purpose sentence and one parameter line, with no wasted words. The most important information is front-loaded.

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?

For a simple retrieval tool with a single parameter and an output schema present, the description is largely complete. It could mention that the output schema will contain the detailed steps, but overall it provides enough to use the tool 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?

The parameter description adds meaning beyond the schema by specifying 'The numeric id, from list_workouts,' clarifying both the type and source. At 0% schema coverage, this is valuable context.

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 'Show the steps of one saved workout plan,' using a specific verb and resource. It distinguishes itself from siblings like list_workouts (list plans) and create_workout (create plans).

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 implies usage requires a workout_id from list_workouts, but does not explicitly state when to use this tool versus alternatives (e.g., get_activity_details). No when-not or alternative guidance is provided.

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