Wake up an agent

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

Annotations already indicate it is not read-only, not destructive, and not idempotent. The description adds authorization class ('board_or_agent') but does not explain behavioral effects like state changes or side effects of waking an agent.

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 extremely concise at two sentences, with no redundant information. However, it could benefit from a bit more substance without losing efficiency.

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?

Given the tool has multiple parameters, nested objects, and enums, the description is severely lacking. It does not explain required fields, parameter purposes, or what happens when the tool is called. The presence of an output schema does not excuse the lack of input context.

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?

With 0% schema description coverage, the description is entirely responsible for explaining parameters. It provides no information about the 'body' fields (source, triggerDetail, reason, etc.) or the required path 'id'. The agent must rely solely on parameter names and enum values, which is insufficient.

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 'Wake up an agent' which is a clear verb+resource pair. However, it does not distinguish from sibling tools like 'resume' or 'pause', leaving ambiguity about when to use this specific action.

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?

No guidance is provided on when to use this tool versus alternatives such as pause, resume, or terminate. The description lacks context on prerequisites or appropriate scenarios.

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