get_scheduled_workouts

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

With no annotations, the description must bear the full burden of behavioral transparency. It conveys a read-only retrieval action and describes the result as a 'calendar,' but it omits details such as response structure, ordering, timezone assumptions, or any access limitations. This is adequate but not rich.

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 is compact and front-loaded with the tool's purpose, then immediately provides the parameter guidance. Every sentence adds value; there is no filler or repetition.

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 two-parameter read-only query, the description is largely complete: it states the resource, the month scope, and primary intended use. It could specify what a 'calendar' entry looks like, but with no output schema that is a minor gap rather than a blocking one.

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 input schema only defines bare integer fields with 0% description coverage, but the description's Args block adds crucial meaning: year must be a four-digit number with an example, and month must be 1-12. Both required parameters are fully clarified beyond the schema.

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 the tool retrieves a calendar of scheduled workouts for a given month, which is a specific verb and resource. It is distinguishable from siblings like list_workouts by focusing on 'scheduled' workouts and a month-level calendar, though it does not explicitly name or contrast a sibling.

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?

It gives clear usage context: 'This is the primary way to find out what's coming up next in training.' This tells the agent when to reach for this tool, but it does not explicitly explain when not to use it or name alternatives.

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