coronium_set_rotation_interval

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

With no annotations, the description carries the transparency burden. It discloses backend polling behavior and the disabling effect of 0, but does not mention whether changes apply immediately, require a restart, or affect ongoing rotations. This is adequate but not comprehensive.

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?

Four short sentences, front-loaded with the core purpose, followed by essential behavioral notes and examples. Every sentence provides value and there is no redundancy or filler.

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 simple configuration setter with a fully documented schema, the description covers the key behavioral aspects (cadence, disabling, backend polling). It lacks explicit return-value or error details, but the absence of an output schema makes that less critical. Overall, it is sufficiently complete for an agent to use correctly.

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?

The input schema already describes both parameters fully (100% coverage), including the '0 = manual only' semantics. The description adds typical value examples (60, 300, 1800) but does not significantly expand beyond the schema, so it meets the baseline without exceeding it.

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 uses a specific verb 'Configure' with a clear resource 'auto-rotation cadence', immediately conveying the tool's function. This distinguishes it from sibling tools like rotate_modem (manual rotation) and get_rotation_status (read-only status).

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?

Provides clear context including typical values and the effect of 0, which implies when to use the tool (to set or disable auto-rotation). However, it does not explicitly reference alternative sibling tools or state when not to use it, so it misses a point for exclusion guidance.

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