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

Annotations already declare destructiveHint=true/openWorldHint=true, and the description adds genuinely new behavioral context: it is a field-selective overwrite ("overwrites selected fields"), it depends on MCP client authorization, and edited content "may appear in a public Space." The public-visibility warning is the kind of consequence annotations cannot express. It stops short of saying what happens to unprovided fields versus null-valued fields, which matters for a partial-update tool.

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, front-loaded with the trigger, then the risk and prerequisite. Every clause carries information: scope, destructive/overwrite semantics, auth dependency, public exposure, required IDs. No filler.

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 mutation tool with no output schema and full annotation coverage, the description supplies trigger, risk, visibility consequence, and ID provenance. What remains thin is update-idempotency/behavior on omitted or null fields, which is relevant given several nullable parameters, but the annotation-plus-description pair is close to sufficient.

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 the schema already documents all six parameters including the list-spaces/list-space-documents provenance note. The description's "Requires numeric space_id and item_id from list-space-documents" largely restates that schema text, so it adds little beyond the baseline.

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-plus-resource: "rename or edit a Space page/document, folder, or external link," and it enumerates the mutable surfaces (markdown, URL, parent folder). It is clear what the tool does, but it never distinguishes itself from the very similar sibling `update-space-document` or from `move-space-item` (which the parent_folder scope overlaps).

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?

Gives a rough trigger ("when the user wants to rename or edit") and a prerequisite (IDs come from list-space-documents), which is real usage guidance. However, with ~15 space-mutation siblings in the list and a near-duplicate `update-space-document`, the absence of any when-not or alternative-selection rule leaves the agent to guess between them.

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