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

Annotations already declare readOnly, idempotent and non-destructive, but the description adds real value beyond them: it states the call is free, that it mutates nothing, and — most importantly — how to interpret the live flag (live means customers already see saved changes, so don't call a change a draft). That is behavioral/interpretive context the structured fields cannot convey.

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?

Four short sentences, front-loaded with what the tool does, then interpretation guidance, then cost, then the usage routing. The live-flag sentence is a bit long-winded but each sentence carries a distinct fact; nothing is 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?

With no parameters and no output schema, the description must carry what comes back — it discloses the live status and how to read it, plus its cost and safety profile via annotations. It does not say whether the page body/design is also returned, which leaves a small gap for a 'get' tool.

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?

The tool takes zero parameters, so the schema imposes nothing to explain and the baseline is 4. The description correctly spends no space on arguments and instead explains the result, which is the right allocation.

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 (Read) and resource (the saved website page) and adds what the response reveals — whether the page is live — so an agent knows the tool is a status/content read rather than a listing. It does not distinguish itself from near neighbours like soclo_page_design_get or soclo_page_preview, which also read page state, so sibling differentiation is only partial.

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?

"Use it with soclo_page_pages and soclo_page_versions to reconcile an uncertain write" gives an explicit trigger condition and names the companion tools. There is no when-not guidance (e.g., when to prefer soclo_page_preview or soclo_page_design_get instead), which keeps it below a 5.

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