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

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint=false, so 'Read only' adds nothing. The rest earns its keep: UTC vs. workspace-local schedule times, the 30-day analytics window, and the non-obvious purpose of share links (so a visit is not attributed to Direct) are behavioral facts an agent cannot get from structured fields, and there is no output schema to carry them.

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?

The content is dense but nearly all of it is load-bearing given the absence of an output schema. The problem is structure: roughly ninety words in a single run-on sentence, with the return-value catalog stacked in one breath and the actionable instruction ('Read it before postfjord_update_page') stranded at the end.

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 rich read tool with no output schema, the description does the heavy lifting by naming every meaningful field group returned, including the timezone-qualified schedules and per-place share links. Missing only error behavior and whether absent fields (e.g. no live page) are omitted or null, which is a minor gap.

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?

There is one parameter (pageId) with 0% schema description coverage, so the schema supplies only a name and a character pattern. The description never mentions pageId, its format, or what happens with an unknown id; the name is largely self-explanatory, which keeps this at an adequate baseline rather than lower.

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?

Opens with a specific verb and resource ('Read only. One page with its content as blocks'), and the parenthetical 'the same blocks the editor has' pins down the shape of the content. It is clearly a single-page read, distinguishable from postfjord_update_page and postfjord_get_analytics by scope, though the purpose statement is immediately buried in a long enumeration of returned fields.

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?

Explicitly instructs 'Read it before postfjord_update_page', which gives a concrete sequencing rule tied to a named sibling. It does not cover failure cases or say when to prefer postfjord_get_analytics instead of this tool for analytics-only needs, so it stops short of full when/when-not guidance.

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