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

Annotations already cover the safe-read profile (readOnlyHint, idempotentHint, destructiveHint=false), and the description adds genuinely useful domain behavior: which settings are immutable (follow updates, capsule placement, brand row, 'Make one') and which single premium setting can vary. It also names the four returned values, which is more than the annotations provide.

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 core content is front-loaded and useful, but the first sentence is a long compound statement about fixed elements, and the final sentence about set_visibility is a non-sequitur for a getter tool that dilutes focus without helping the caller invoke it.

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 correctly compensates by enumerating the returned fields (plan, workspace_capsule, page_capsule, manifest_capsule, effective_capsule) and their value domains. Combined with the documented optional parameter, an agent has enough to call it correctly; only the omission of any note about the corresponding setter is a 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?

Schema description coverage is 100% and the sole parameter's meaning ('Which page; omit to read only the workspace default') is already fully documented in the schema. The description's 'Omit proposal_id to read only the workspace' restates that same fact rather than adding format or edge-case detail, 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?

The description states a specific verb+resource ('Read the reader side back') and enumerates exactly which reader-side settings are fixed versus settable, so an agent knows what it is reading. It never names the sibling set_reader_view, so it stops short of explicit sibling differentiation, but the read framing is unambiguous.

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?

'Omit proposal_id to read only the workspace' gives clear conditional usage for the single parameter. However, there is no routing guidance to the obvious sibling set_reader_view for changing these values, and the trailing mention of set_visibility is a tangential aside rather than an alternative-selection rule.

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