routines_create

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

Description discloses that timezone defaults to UTC and creation is non-destructive. No contradiction with annotations (readOnlyHint=false, destructiveHint=false). Side effects like permission checks are not mentioned but acceptable.

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: first on purpose, second on usage. No waste, front-loaded, easy to parse.

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?

Fully explains scheduling parameters and timezone. Omits details about required params (name, skill_id, project_id) but those are evident from schema. No output schema, but return type likely an ID.

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?

With 43% schema description coverage, the description adds value by clarifying mutual exclusivity of schedule_preset and cron_expression, and reinforcing timezone defaults. Partially compensates for schema 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?

Description states 'Create a new Routine. Schedules a Skill to run on a cron expression.' This is a specific verb-resource pair, clearly distinguishing it from sibling tools like routines_list or routines_delete.

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?

Explicitly instructs to use either schedule_preset or cron_expression, clarifying the two scheduling options. No when-not-to-use guidance, but adequate for a creation tool.

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