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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the description's lower bar is met and exceeded by adding two behaviors not in the structured data: long command output is truncated, and a full detail read lives elsewhere. It also enumerates the status lifecycle, useful for interpreting results.

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?

Two tight sentences plus the endpoint path, with the resource, payload fields and truncation caveat all front-loaded. No filler or repetition of the title.

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?

With no output schema, the description carries the return-shape burden and does so adequately by naming the fields returned (actor, status, timestamps) and the truncation behavior; pagination is covered by the schema. Only minor gaps remain, such as ordering or default recency window.

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% and both parameters (page, limit) are fully documented in the schema, including the 'Pass the previous reply's next_page' guidance. The description adds no parameter-level detail, so the baseline of 3 applies.

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?

Specific verb+resource with the content spelled out: 'List recent events (the activity log: provisioning, restarts, deploys, cache purges)'. It distinguishes itself from the sibling spinupwp_get_event by noting that detailed output belongs there.

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?

'read one event for its full output' explicitly routes the agent to spinupwp_get_event when full command output is needed, which is the key alternative. No explicit when-not conditions or other exclusions are given, but the primary disambiguation is present.

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