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

Annotations already signal readOnly, idempotent, and non-destructive behavior. The description adds useful behavioral context beyond that: the tool only covers completed processes, it is paginated with defaults, and it excludes certain content types. This is meaningful added context without contradicting the annotations.

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 description is tight and front-loaded: it leads with the tool's core purpose and return contents, then quickly explains pagination and gives the key routing guidance. No sentences are wasted and the most important discriminator is stated early.

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, no-required-param, paginated list tool, the description is complete: it names the return contents, scoping, pagination behavior, and the correct alternative for single-process detail. The absence of an output schema is compensated by the explicit enumeration of the response fields.

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%, so the schema already documents all parameters well. The description restates pagination defaults that appear in the schema and does not add substantial new meaning to any specific parameter. Baseline 3 is appropriate because the schema carries the burden.

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 action ('cross-process portfolio digest') and enumerates exactly what it returns: per-process summary, SWOT, projected impact, and a step skeleton. It also distinguishes this tool from getClarityProcessSnapshot, which covers single-process detail, so an agent can select among siblings without opening schemas.

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 description gives explicit guidance: use this tool to answer portfolio-wide questions in one pass, and use getClarityProcessSnapshot only for the few processes that need full detail. It also states what this tool intentionally omits (step prose and source excerpts), which tells agents when not to use it.

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