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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered. The description adds genuine value on top: deletion happens 'directly after the MCP client authorizes the call' and may affect items 'publicly visible in a public Space.' It omits reversibility/recovery guidance, which keeps it below a 5.

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 sentences with no filler, and the trigger condition is front-loaded ahead of the destructive-action warning and the parameter note. Slightly dense but every sentence carries distinct information.

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 destructive bulk-delete tool with complete schema coverage and annotations, the description covers the trigger, the destructive/authorization behavior, the public-visibility risk, and ID sourcing. No output schema exists, so return-value explanation is unnecessary; only recovery/irreversibility detail is missing.

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 coverage is 100%, so both parameters are already documented; that sets a baseline of 3. The description adds sourcing meaning beyond the schema by telling the agent item_ids should come from list-space-documents, which is useful invocation guidance not present in the structured fields.

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 (delete) and the full resource scope (Space pages, documents, folders, external links), including the bulk 'one or more' nature. This distinguishes it from single-item siblings like delete-space-document and from delete-space, so an agent can route correctly without opening a 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?

Opens with an explicit trigger ('Use this when the user wants to delete...') and names the exact item types in scope, plus a pointer to list-space-documents for obtaining IDs. It lacks an explicit when-not statement (e.g., versus delete-space-document), so it stops short of the top score.

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