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

The description explicitly calls this a 'read-only tool', while the annotations declare readOnlyHint=false — a direct conflict about whether state can be modified. Despite otherwise helpful disclosure (grouping by evidence class, not_determinable/outside_review_scope qualifiers, disclaimer_md handoff requirement), the contradiction is serious enough to anchor this dimension at 1.

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?

Short titled paragraphs, front-loaded with what the tool returns before the parameter and availability notes. Slightly more prose than strictly necessary (the empty-group caveat and disclaimer sentence are long), but every sentence carries non-obvious information.

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?

An output schema exists, so return values need not be re-specified, yet the description still usefully explains the grouping semantics, qualifier fields, and the disclaimer_md obligation. The one real gap is the failure to reconcile its 'read-only' claim with the annotations.

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 must carry the load, and it does: limit's default of 25 and cap of 100, and include_all's inclusion of resolved/dismissed/out-of-scope records. Only project_id is left unexplained, which is self-evident from the name and required list.

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 opening sentence gives a specific verb (read) and resource (a project's security-control observations and review boundaries), which cleanly separates it from the mutating sibling run_control_gap_review. It stops short of naming that sibling explicitly, but the read/compute split is inferable.

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 conveys operational context (limit default/max, include_all behavior, availability after the project's trigger closes) but never states when to prefer this over run_control_gap_review, which is the obvious alternative sitting in the sibling list. Usage is implied rather than routed.

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