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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds real value beyond that by disclosing the bounded-page pagination model and that brief IDs link to editorial runs. It stops short of saying what a brief record contains or what happens at the end of the cursor chain.

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?

Three short sentences, zero filler, with the core purpose front-loaded and the pagination mechanic immediately after. Every sentence carries information an agent needs.

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 three-parameter read-only list tool with no output schema, the description covers purpose and pagination adequately, and 'Brief IDs link to editorial runs' hints at the return shape. It remains incomplete on the required projectId parameter and on how this list differs from the generic list_briefs sibling.

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 0%, so the description carries the burden. It does explain cursor semantics ('pass nextCursor as cursor') and gestures at limit ('bounded pages'), which is meaningful compensation, but projectId — the only required parameter — is never explained, and no defaults or bounds are given for limit.

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 and resource — 'Recover persisted authored briefs for a project' — which is more concrete than a bare 'list'. It does not, however, explicitly distinguish itself from sibling list_briefs or suggest_briefs, so the agent must infer that 'editorial' scoping is the differentiator.

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?

Provides procedural guidance for pagination ('pass nextCursor as cursor until done'), which is genuinely useful. But it never says when to choose this over list_briefs or editorial_list_runs, and states no prerequisites or exclusions.

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