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

Annotations already declare readOnly, idempotent, non-destructive, non-open-world. The description adds genuinely new behavioral context: 'decisions never rewrite text or grant final approval', 'A new draft requires new review once adopted', and the authorization boundary 'This tool cannot impersonate a human reviewer'.

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 read purpose is front-loaded, but six dense sentences mix reading, workflow, and constraints, and jargon like 'without requiring adaptive sheets' adds noise. Several sentences earn their place; a few are tangential or ambiguous.

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 read-only tool with annotations covering the safety profile and no output schema, the description supplies workflow context, hard constraints, and output fields (portalPath, pagination.nextOffset) an agent would otherwise lack. The thin parameter explanation is the main gap, but overall it is complete enough to call 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 description coverage is only 17% (only projectId documented), so the description must compensate. It gestures at pagination (offset/limit) and expectedDraftRevision, but never explains filter's enum values (pending/confirmed/rejected/supplemented), limit bounds, or sectionId, and its 'echo draftRevision' wording does not match the nested expectedDraftRevision {outputJobId,payloadHash} structure.

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?

It names a specific verb (read) and resource (the saved draft's factual sentences, frozen sources, and exact-version human decisions), which is more than a tautology. It does not, however, distinguish itself from similarly named siblings like helvabase_read_draft_review_history or helvabase_read_draft_review_source, so the agent must infer the boundary.

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?

It gives procedural context ('Follow pagination.nextOffset and echo draftRevision', 'Share portalPath for human confirmation') and a downstream workflow ('Reconcile feedback into a new sourced draft'). It never states when to prefer this tool over read_draft_review_history/source or what prerequisites exist, so usage is implied rather than explicit.

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