Resume slot

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

With no annotations, the description carries the full burden and does disclose meaningful behavior: unpausing, messaging every agent on the slot, and that agents re-read the page and continue. It stops short of covering state preconditions (e.g. error when the slot isn't paused) or permissions, so it is strong but not exhaustive.

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?

Three tight sentences with zero waste, and the critical usage constraint is front-loaded ahead of the behavioral and bulk-mode details.

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 4-param, all-optional tool with no annotations and no output schema, the description supplies the usage rule, the observable effect, and the bulk-mode behavior. It omits only edge-case behavior (resuming an already-active slot, failure modes), which is a minor 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?

Schema description coverage is 100%, so slot/slots/agent are already fully documented in the schema (including the port-subtraction hint). The description only adds a semantic gloss for 'all=true resumes every paused slot,' which is close to restating the schema's 'All paused slots.' Baseline 3 applies when the schema does the heavy lifting.

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 and resource: 'Unpauses and messages every agent on the slot to wake it.' It clearly contrasts with the sibling slot_pause by describing the inverse operation and the wake-up effect, so an agent can distinguish it without opening either schema.

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?

Explicitly names the trigger ('only when the user says to resume, e.g. continue 3') and an exclusion ('the agent owning a paused slot never calls it on its own'). It also routes the bulk case via 'all=true resumes every paused slot.' Both when-to-use and when-not-to-use are covered.

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