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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds real value by disclosing pagination behavior and a response field ('nextCursor') that has no output schema, plus a warning to retain evidence IDs, supersession and uncertainty when recovering decisions. It does not state ordering, page size behavior, or what an empty page means.

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?

Two sentences, front-loaded with the read operation and then the pagination/retention instructions; nothing is obviously redundant. It is somewhat dense with internal jargon, but the information per sentence is high.

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, three-parameter paged list with no output schema, the description covers pagination and key result concepts (evidence IDs, supersession, uncertainty) but omits the run scoping, limit semantics, and ordering. An agent can call it, but must infer what defines the result set.

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 only 33%: runId is documented merely as 'runId (path)' and limit/cursor are undocumented in the schema. The description partially compensates by explaining cursor semantics ('pass nextCursor as cursor until done'), but it says nothing about the runId scoping requirement or the limit bounds (1-100).

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 says it reads 'durable observations ... in bounded pages', which conveys a list/read operation but substitutes jargon ('observations', 'useful/nothing-useful/uncertain outcomes') for the resource name 'findings', and never states that results are scoped to a run. It gives no differentiation from close siblings such as editorial_list_evidence, editorial_get_run, or editorial_findings_append.

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?

The pagination instruction ('Pass nextCursor as cursor until done') is a concrete procedural usage cue, which is more than most list tools offer. However, there is no guidance on when to choose this tool over editorial_list_evidence or editorial_get_run, and no stated preconditions or exclusions.

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