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 fully structured. The description adds one behavioral detail — that results are 'privacy-filtered' — but does not elaborate on what that filtering means (permission-based, redaction, row limits) or on pagination.

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?

A single front-loaded sentence with the verb leading, and no wasted words. It is appropriately terse, though the awkward 'hosted list findings' phrasing keeps it from being a clean 5.

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?

This is a read/list tool with no output schema, so the description is the only place an agent can learn what is returned. It omits return shape, pagination, ordering, and what 'privacy-filtered' actually filters, leaving significant gaps for a 3-parameter listing tool.

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 carries the parameter documentation burden and the baseline is 3. The description adds no parameter-level meaning (e.g., what sessionId versus executionId scope), so it does nothing beyond what the structured fields already provide.

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 verb (read) and resource (findings) are present, and the description hints at scoped project metadata, but the phrase 'Read hosted list findings' is grammatically garbled and does not clearly distinguish this from list_reports, list_investigations, or the sibling create/update/delete_finding tools. An agent can infer the general purpose but gets no help routing among the many list-family siblings.

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?

There is no statement of when to use this tool, when not to, or which alternative to prefer over the many sibling list_* tools. Usage is left entirely to inference from the name.

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