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

Annotations already declare this a safe, idempotent, read-only, non-open-world operation, so the safety profile is covered. The description adds genuine value beyond them by disclosing what the response contains (canonical bugs, current status, evidence, queue progress), which matters because there is no output schema. It omits any pagination or volume behavior.

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 that names the action, the resource, and the returned content with no filler or repetition. Every clause carries 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?

For a read-only list tool with full annotation coverage and no output schema, the description adequately covers what is returned. It stops short of explaining result ordering, volume, or how the optional sessionId/executionId filters change 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 description coverage is 100%, so all three parameters carry their own documentation and the baseline is 3. The description adds no parameter-level meaning at all, and notably does not clarify how sessionId/executionId narrow the listing or how they interact with the required projectId.

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 gives a specific verb (Read) and resource (owned narrative reports and their canonical bugs) plus the payload scope (status, evidence, queue progress). It does not name or distinguish itself from the sibling read tool get_report, so an agent must infer the list-vs-single distinction from the name alone.

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 when-to-use guidance: nothing states when to call list_reports versus get_report, list_findings, or list_investigations, and no prerequisites or exclusions are given. The only usable cue is the adjective 'owned', which is scope, not usage routing.

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