openmausbot_set_routine_enabled

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

Annotations already establish that this is not read-only, is idempotent, and is non-destructive. The description adds a plan/apply mode that annotations do not convey, but it does not explain what planning entails or what side effects applying has beyond the schema's dry_run flag.

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?

A single sentence with no filler or repetition. The core subject, the routine's enabled state, is front-loaded, and every word contributes to the meaning.

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?

For a state-changing tool with a critical dry_run default, the description omits the most important call behavior: by default the tool plans rather than applies. Given the large set of routine-management siblings, this under-specification creates a real risk of misuse.

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 only 33%, with enabled and dry_run having no schema descriptions. The description's 'Plan or apply' loosely maps to dry_run, but it never states that dry_run defaults to true or that setting it to false is what actually applies the change.

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 names a specific action ('Plan or apply') and a specific resource ('one routine's enabled state'), which is enough to distinguish it from listing, running, creating, or deleting routines. It is clear without being as explicit as the annotation title 'Enable or disable an OpenMausBot 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?

There is no guidance about when to use this tool versus alternatives like run_routine_now, upsert_routine, or list_routines. The 'Plan or apply' phrasing hints at two modes, but no explicit conditions or exclusions are given to help an agent choose correctly.

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