motion_recurring_tasks

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

No annotations are provided, so the description must fully disclose behavioral traits. It fails to mention side effects (e.g., whether creating a recurring task automatically generates occurrences), authentication requirements, or rate limits. The minimal detail leaves significant gaps for a CRUD tool.

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?

The description is concise: one introductory sentence followed by a compact list of required params per operation. Every sentence adds value without redundancy.

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 15 parameters, no output schema, and nested objects, the description covers only required params for operations. It omits guidance on optional params and return values. Schema descriptions help, but the tool description alone is not fully complete.

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 100%, so the baseline is 3. The description adds minimal extra meaning beyond listing required params per operation; it does not elaborate on optional parameters or the frequency object's structure, which the schema already covers.

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 'Manage recurring tasks' and lists three distinct operations (list, create, delete), specifying required parameters for each. This differentiates from sibling tools like motion_tasks which likely handle non-recurring tasks.

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 provides explicit required parameters per operation, guiding the agent on what to supply. However, it does not explicitly state when to use this tool versus alternatives like motion_tasks, though the sibling names imply context.

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