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

Annotations flag destructiveHint=true and openWorldHint=true, and the description explains exactly why: "A siteId replaces the page at the same address" discloses the destructive replacement behavior. It also adds the 4 MB decoded size cap, the private-by-default visibility, and that the original is preserved for download – substantial context beyond the annotations.

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-loaded with the core action and format list, then progressively adds size, rendering, and replacement details. Most sentences earn their place, though the middle sentence on PDF/slide/spreadsheet rendering is mildly descriptive padding rather than decision-critical 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?

With an output schema present, return values need not be explained, and the description still covers formats, size limits, default visibility, replacement semantics, and the no-invitation behavior. An agent has everything needed to invoke it correctly.

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 baseline is 3, but the description adds real constraints not in the schema: the 4 MB decoded limit and that content must be base64 bytes ("not a local path or URL" is reinforced). It also clarifies the siteId replacement semantics beyond the schema's short note.

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?

The description names a specific verb (publish) and resource (file → browser-viewable page) and enumerates the accepted formats, so the agent knows exactly what the tool consumes and produces. It does not, however, name or distinguish itself from close siblings like publish_page or publish_anonymous_page, leaving that routing to inference.

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?

"private by default" and "Does not send invitations" give clear contextual boundaries, implicitly steering the agent away from send_page/notify_recipients when no notification is wanted. There is no explicit when-not or named alternative, so the guidance is contextual rather than directive.

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