List guides

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

The readOnlyHint annotation already signals a safe read operation, so the bar for additional transparency is lower. The description adds 'stored on the configured backend' but does not disclose pagination behavior, default limits, ordering, or whether the list is comprehensive.

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 a single, well-structured sentence that directly states the tool's purpose. No wasted words or redundancy.

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?

With no output schema and a paginated list operation (limit/offset/since), the description is too sparse. It does not mention return format, whether results are ordered, or how pagination works, leaving the agent guessing about the actual invocation behavior.

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?

Schema description coverage is only 33% (only 'since' is described). The tool description adds no explanation for limit, offset, or since. It fails to compensate for the low schema coverage, leaving agents uncertain about how parameters affect results.

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 a specific action ('List') and resource ('structured workouts') plus context ('configured backend'). It distinguishes from siblings: preview_workout implies a focused view of a single workout, and describe_backend is about backend metadata, whereas this tool returns a list.

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?

No guidance is provided on when to use this tool versus its alternatives. There is no mention of exclusions, prerequisites, or situations where preview_workout or describe_backend would be more appropriate.

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