services_enter_rescue_mode

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

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the risk profile is visible. The description adds nothing beyond the raw endpoint path: it does not say what rescue mode changes (boot environment, availability, existing state), whether it triggers a reboot, or that a separate call is needed to return to normal operation. For a destructive mutation, that is a real gap.

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?

Very short and front-loaded, with no wasted prose. However, the phrasing 'Enter to rescue mode' is awkward and the second line is a raw endpoint dump that consumes half the available space without adding agent-facing meaning.

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 a single-parameter tool with no output schema and annotations that cover the safety profile, the definition is nearly adequate but still lacks the operational consequences of entering rescue mode and the exit path via the sibling tool. An agent could call it correctly but not safely or fully informed.

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?

Only one parameter (id) with 0% schema description coverage. The URL template POST /services/{id}/rescue does implicitly identify the parameter as the service identifier, which is genuine meaning beyond the bare {"id": number} schema, but no format, range, or validation detail is added.

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 verb and resource ('Enter to rescue mode' on the service at POST /services/{id}/rescue), so an agent can tell it puts a service into rescue mode. It stops short of differentiating from the sibling services_leave_rescue_mode, but the operation itself is unambiguous.

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?

There is no when-to-use guidance, no prerequisites, and no mention of services_leave_rescue_mode as the way back out. The agent is left to infer that this should be paired with the leave tool and that it affects a single existing service.

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