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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, so the safety profile is covered. The description adds genuinely new behavioral context: the default read is bounded and complete (~1-2 KB), outline is character-capped, and full is the entire cleaned JSON — useful cost/fidelity signaling for a read 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?

Front-loads the read purpose, then the before/after discipline and the copy scoping rule. Four sentences with little waste, but dense enough that each clause has to be parsed carefully rather than skimmed.

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?

There is no output schema, so the description carries the return-format burden and does so: it describes the section list with target path, text preview and descendant count, and characterizes the size/fidelity of each detail mode. Nothing an agent needs to call and interpret it 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 baseline is 3, but the description goes beyond the schema by explaining how the two parameters interact — detail: full should be paired with targetPath of the single section being copied, and targetPath scopes the read to one subtree instead of the whole page.

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 and resource — reading the current page structure and addressable component target paths — which is clearly distinct from siblings like read_selection (current selection) and list_pages (page inventory). The description's mention of target paths tells the agent this is the tool that reveals edit coordinates.

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 explicit before/after triggers: call before editing a named or relative component that is not the current selection, and again after applying edits to verify. It also gives a when-not: for copying, use detail: full with a single targetPath rather than a whole-page read. An agent can sequence its calls without guessing.

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