List project feedback

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

Annotations already declare the safety profile (readOnlyHint=true, idempotentHint=true, destructiveHint=false). The description adds content context about the feedback being 'page-anchored' and 'with explicit human or external-agent attribution', but it does not disclose additional behavioral traits such as pagination, filtering defaults, or return structure beyond what the schema already provides. No contradiction with 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 a single sentence that immediately states the action (Read) and the target (page-anchored review feedback for versions in a project). It is concise and front-loaded, with every word contributing meaning.

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?

The tool has strong schema coverage and annotations, and the description clearly communicates the core purpose and scope. However, since there is no output schema, a brief mention of the return format (e.g., a list of feedback items) would have made it complete. The description is still adequate for a simple read-only 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?

The schema descriptions for 'project_id' and 'include_resolved' achieve 100% coverage, so the baseline is 3. The description does not add any additional meaning to the parameters beyond what the schema already explains, such as the default behavior of 'include_resolved' or the format of 'project_id'.

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 uses the specific verb 'Read' and identifies the resource as 'page-anchored review feedback for versions in a project'. It further distinguishes this from other feedback tools by noting 'explicit human or external-agent attribution', which differentiates it from generic feedback operations and sibling tools like add_project_feedback and resolve_project_feedback.

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 clearly implies the use case: reading review feedback for project versions. It provides context about what the tool returns (page-anchored feedback with attribution), but it does not explicitly state when to use this versus alternatives such as add_project_feedback or resolve_project_feedback, nor exclude other feedback-related tools.

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