Turn off or on

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

Beyond the annotations, the description explains the real-world effects of turning off (link stops answering, workers.dev address lost, tunnel returns an off page), explicitly states nothing is deleted, and confirms toggling back on restores the same link, key, and sign-in. This adds substantial behavioral context.

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 front-loaded with the core action, then expands into off/on behavior, the remove alternative, and a UI hint. Every sentence carries useful information without padding.

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 two-parameter boolean toggle, the description covers behavior, reversibility, idempotency, and sibling-tool routing. No output schema is present, but the return value is not essential for deciding how to call this tool.

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 coverage is 100%, so the description need not re-document parameters. It adds value by clarifying that on=true brings back the exact same link with the same key and sign-in, and that off is non-destructive, going beyond the schema's brief boolean descriptions.

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 states a specific action ('Turn a cloudfact off, or back on') and defines exactly what 'off' means at the resource level. It also distinguishes itself from remove, so an agent can tell these siblings apart immediately.

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?

It gives explicit guidance: 'Prefer this over remove when the user wants something "off" or "down" rather than gone.' It also notes that deploying again turns it on, which clarifies an alternative path with the same effect.

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