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

Annotations already flag destructiveHint=true, readOnlyHint=false and idempotentHint=false; the description adds the crucial nuance that destruction is scoped — an existing page's draft is replaced only when replace is true. It doesn't cover permission requirements or failure behavior, so it stops short of 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?

Two tightly packed sentences, front-loaded with the operation and accepted formats, then the create-vs-replace conditions. 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, the description covers inputs, creation vs. replacement conditions, and the destructive scope. Gaps remain on return values and error handling, but the essential calling contract is complete.

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 67% with 'file' documented as brief-or-page-JSON plus a format doc link; the description adds meaning to the two undocumented-ish params by tying username to the create path and replace to draft overwrite. It doesn't clarify what the response is, but for parameters it adds real value over the schema.

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 (load/import) and resource (whole page) plus the two accepted input formats (Posy brief with name/bio/look/theme/links[], or full page JSON). It partially distinguishes itself from the create_page sibling by describing the create-if-missing path, but never names create_page as 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?

Gives conditional routing: pass username when there is no existing page, and replace-respecting behavior when one exists. This is clear when-to-use context, but no exclusion or named alternative (e.g., 'use create_page instead for a blank page') is provided.

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