get_scheduled_workout_by_id

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds one genuinely non-annotation fact: this tool hits /workout-service/schedule rather than /calendar-service, which implies a different backend and possibly different auth or failure behavior, but it discloses nothing about what is returned or about error conditions.

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?

A single short clause, so there is no bloat — but it is under-specified rather than concise. The one sentence spends its words on an endpoint distinction instead of front-loading what the tool actually retrieves.

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 one-parameter read tool with full schema coverage and annotations covering the safety profile, no output schema is required and the missing return description is acceptable. What is missing is any statement of what distinguishes a 'scheduled workout' lookup from the other scheduled-workout siblings beyond the internal base URL.

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 a single parameter, 100% schema coverage, and the schema stating 'Numeric id', the schema already does the work. The description adds nothing about id format, accepted string-vs-integer forms, or valid ranges, so the baseline 3 applies.

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 never states what the tool does — it only notes that it uses a different service base than getScheduledWorkouts. The name implies fetching a single scheduled workout by id, and the sibling comparison confirms it is distinct from the list variant, but the verb/resource is left to inference from the name alone.

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?

There is no explicit when-to-use guidance or prerequisite. The base-URL contrast with getScheduledWorkouts hints that the two are not interchangeable, but it is an implementation detail rather than a routing rule an agent can act on when choosing between them.

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