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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the description is not carrying the safety burden. It adds genuinely useful context the annotations cannot convey: that the call consumes Assist credits and what the ~1KB payload contains. It does not, however, discuss failure modes or the cost magnitude.

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 key differentiator ('OFFLOAD reading a WordPress page') and stays tight overall. The parenthetical aside about wp_get_page's cost is slightly verbose but earns its place by justifying the tool's existence.

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?

With no output schema, the description carries the return-shape burden and does so precisely: semantic section types, one-line summaries, flat editable-element skeleton, and SEO gaps. An agent knows both inputs and outputs before calling.

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 site_id and post_id (with their provenance hints) are already fully documented. The description adds no syntax or format detail beyond what the schema provides, so the baseline 3 applies.

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 (read a WordPress page as a compact digest) and explicitly contrasts itself with the sibling wp_get_page. The output contents (sections, editable-element skeleton, SEO gaps) make the tool's scope unmistakable.

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 an explicit when-to-use (instead of wp_get_page) and names concrete next-step tools (assist_edit_section, wp_patch_page) that consume the element ids. The routing logic from digest to edit is spelled out, leaving nothing to inference.

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