shelly_schedule_create

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

Describes validation of timespec, device limit, and method; audit logging. Adds behavioral context beyond idempotentHint annotation. Does not mention failure behavior or side effects.

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. Could improve readability with bullet points.

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?

Provides validation context and logging, but does not explain return values (output schema exists). Lacks details on 'calls' structure beyond schema.

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?

Adds meaning to 'timespec' and 'calls' parameters not in schema, but does not describe 'device' or 'enable'. Schema coverage is 0%, so description partially compensates.

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?

Clearly states 'Create a schedule' with specific resource and key parameters (timespec, calls). Distinguishes from sibling tools like shelly_schedule_update and shelly_schedule_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?

Implies usage for creation but lacks explicit guidance on when to use vs alternatives or when not to use. No statements about prerequisites or context.

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