rotate_docker_keys

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

With no annotations, the description carries the burden and does meaningful work: it discloses that existing certificate exports stop working and that the sandbox will restart — both important side effects an agent should know before invoking. It omits return value and any auth/permission requirements.

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?

Front-loads the purpose, then adds the certificate details and side effects, closing with the HTTP endpoint. Efficient and well ordered, though the '(enable / rotate)' framing and raw endpoint line add minor 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?

For a single-parameter action tool with no output schema or annotations, the description covers the key effect (new certs) and the disruptive side effects (old exports invalidated, sandbox restart). Only the return payload and permission requirements are unaddressed, which is a modest gap.

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?

One parameter ('name') with 0% schema description coverage, so the description must compensate. Context ('the sandbox's Docker API') makes it clear 'name' is the sandbox name, but it is never stated explicitly. Baseline 3 for the near-trivial single input.

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?

States a specific verb+resource: it issues new Docker access certificates (CA, server, client) for the sandbox's Docker API, naming the endpoint POST /sandboxes/{name}/docker-keys. The '(enable / rotate)' parenthetical slightly muddies whether this is one action or two, but the resource and effect are unambiguous and no sibling tool overlaps.

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 the use case (you need fresh Docker certs) and warns that earlier exports stop working, but never states explicitly when to call this versus leaving existing certs alone, nor prerequisites. Usage is inferable rather than spelled out.

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