get_routines

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

With no annotations provided, the description must fully disclose behavior. It only states that it returns a paginated list, but does not explain the return structure, pagination details (e.g., defaults, max page size), or whether any side effects exist. For a read-only tool, this is thin but not misleading.

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, front-loaded sentence that directly states the tool's action and result. There is no redundant wording or filler, and every word contributes meaning. It is appropriately sized for a simple list operation.

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?

Given the simplicity of the tool (2 optional params, no output schema, no annotations), the description is minimal but leaves out important context such as the shape of the returned list, whether pagination is mandatory, and what fields each routine entry contains. It is not complete enough for an agent to use confidently without additional assumptions.

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 schema has two parameters (page, pageSize) with no descriptions, and the description does not explain their meaning beyond the word 'paginated'. With 0% schema coverage, the description fails to compensate by clarifying how these parameters control pagination, defaults, or constraints.

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 verb 'Get' and the resource 'routines', and mentions 'paginated list', which distinguishes it from get_single_routine and get_routine_folders. However, it does not explicitly specify what scope of routines (e.g., all routines, user-specific), but the core purpose is unambiguous.

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 guidance on when to use this tool versus alternatives. The description does not mention any exclusions, prerequisites, or explicit comparisons with sibling tools like get_single_routine or get_workouts. Users are left to infer usage from the tool name.

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