Start today's routine

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

No annotations provided, so the description must carry the behavioral burden. It states logs are 'completed' but does not disclose idempotency, overwrite behavior, or how defaults interact. The meaning of 'minimum routine' is vague.

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, front-loaded with purpose, no wasted words. Highly concise and easy to scan.

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 8 parameters with defaults and no output schema, the description is too brief. It does not explain the 'minimum routine' concept, how parameters are combined, or what the resulting log looks like. Users would need to infer from defaults.

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 coverage is 50% with 8 parameters, but the description only mentions templateId. The other 7 parameters with defaults are not explained beyond the schema. The description fails to add meaningful context for parameters like sitToStandReps or walkingMinutes.

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 tool logs a minimum routine for today, using verbs like 'start/log shortcut' and 'logs the minimum routine'. However, it does not distinguish from similar sibling tools like ryot_log_minimum_workout, which likely serves a similar purpose.

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 explicit guidance on when to use this tool versus alternatives or when not to use it. The description only mentions optional template linking but lacks context for choosing this tool over other logging or routine creation tools.

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