create-routine

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

With no annotations, the description must fully disclose behavior. It states the creation action and return of full routine details including ID, but omits side effects, auth needs, error handling, or constraints like duplicate titles. Basic but not 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?

Two well-structured sentences front-load the purpose, then list requirements, optional features, and return value. No redundant words, every sentence adds value.

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 complex nested schema (exercises with sets having many fields) and no output schema or annotations, the description is insufficient for an agent to correctly construct all parameters. It lacks detail on exercise and set structure, making it hard to use without additional knowledge.

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%, so the description must compensate. It only mentions title, exercises (with sets requirement), and optional folderId. It does not explain nested properties like set types, notes, supersetId, or restSeconds, leaving significant gaps.

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 explicitly states it creates a new workout routine, distinguishes from siblings like 'update-routine' and 'create-workout', and clearly identifies required elements (title, exercises with sets) and optional folder assignment.

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 implies when to use (when creating a new routine) but provides no explicit guidance about when not to use it or which sibling tool to choose instead. No alternatives or exclusions are mentioned.

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