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

Annotations already declare destructiveHint=true and openWorldHint=true, but the description adds rich operational detail beyond them: it specifies the external-provider state change, attempts webhook removal after authorization, and the effect of stopping provider events from reaching Autopilot. It also lists Enterprise access and manageable Space permission as prerequisites, which is exactly the kind of behavioral context an agent needs.

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 sentences with zero waste; the usage trigger is front-loaded, followed by the side effects and prerequisites. Every clause earns its place and no information is repeated unnecessarily.

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 two-parameter mutation with no output schema, the description covers purpose, trigger conditions, destructive side effects, authorization requirements, and access prerequisites. An agent has enough to decide when and how to call it, and no return-value explanation is needed since no output schema exists.

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 the schema itself documents both parameters with useful notes (e.g., 'Use list-space-repository-links first when needed' for link_id). The description merely restates that space_id and link_id are required, adding no meaning beyond what the schema already provides. Baseline 3 is appropriate when the schema carries the semantic load.

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 (disable) and resource (Autopilot repository link for a Space), and the phrasing 'pause, turn off, or disable' signals a reversible action that contrasts with permanent deletion. It does not explicitly name the sibling delete-space-repository-link, so an agent must infer the distinction from the name rather than being routed to the alternative.

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?

Provides clear when-to-use context ('Use this when the user wants to pause, turn off, or disable...'), which covers the common trigger. It does not explicitly state when not to use this tool or name the alternative (delete-space-repository-link for permanent removal), so an agent has no direct exclusion guidance.

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