list_routines

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

With no annotations provided, the description must disclose behavioral traits. It mentions one constraint (max pageSize of 10) but does not describe the return format, pagination behavior, authentication requirements, or the fact that this is a read-only operation. This is a significant gap for a tool with no safety hints.

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 two concise sentences, front-loaded with the primary purpose, followed by a relevant constraint. Every word adds value, with no fluff 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?

The tool is simple with two optional parameters and no output schema. The description gives a basic understanding of the operation and a key constraint, but lacks details about the response structure or pagination behavior. This is adequate for a simple list operation, but not complete enough for an agent to predict the full output without further context.

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 0%, and the description only mentions pageSize's maximum, providing no additional meaning for the page parameter. Although the schema itself includes defaults and constraints, the description does not help an agent understand the semantics of pagination parameters beyond what the schema already declares.

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 'List' and the resource 'saved routines (workout templates)', distinguishing it from sibling tools like list_workouts (which likely lists workout sessions) and get_routine (single routine fetch). This is a specific and unambiguous purpose statement.

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 does not explicitly state when to use this tool versus alternatives, but the name and resource type imply it is for browsing all routines, contrasting with get_routine for a single routine. The note about pageSize being capped at 10 gives a practical usage hint, but no exclusions or alternative tool references are provided.

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