update-routine

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

No annotations provided. Description says it returns updated routine but does not disclose side effects, error handling (e.g., if routineId not found), auth requirements, or rate limits. Basic behavioral info only.

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 sentences, no unnecessary words. Directly states purpose, modifiable fields, and return value. Highly concise.

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?

Parameter count 4 with complex nested exercises array, no output schema, no annotations. Description fails to explain exercise configuration structure, partial update behavior, or validation rules. Incomplete for a mutation tool with nested data.

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?

Description mentions title, notes, and exercises but omits routineId (only implied 'by ID'). With 0% schema coverage, description should comprehensively explain each parameter; it only gives a brief list without clarifying structure 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?

Description clearly states verb 'Update', resource 'routine', and scope 'by ID', listing modifiable fields (title, notes, exercise configurations) and return value. Differentiates from siblings like create-routine and get-routine.

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?

Implies usage when modifying an existing routine, but no explicit guidance on when not to use or alternatives. Lacks context for prerequisites or conditions.

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