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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds the phrase 'using privacy-filtered project metadata', which suggests the results are scoped by privacy permissions—a useful behavioral hint. However, it does not mention pagination, sorting, or whether the list is complete, so it adds only modest value beyond 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 with no redundant filler, front-loading the action. It is appropriately concise, though the phrasing 'hosted list change reviews' is slightly awkward and could be clearer. No wasted words, so it earns a 4.

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?

With no output schema, the description should describe what is returned, but it does not. It also fails to explain the six parameters given zero schema coverage. The tool appears to be a list operation, but there is no mention of response shape, error conditions, or required context. This is inadequate for an agent to call it correctly without further inference.

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 compensate by explaining parameter purposes, but it does not. The parameters projectId, cursor, pageSize, reviewId, sessionId, and executionId are entirely undocumented. The phrase 'project metadata' hints at projectId's role but does not clarify the others, leaving the agent to guess at cursor/pageSize for pagination and the filter parameters.

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 clear action ('Read') and resource ('hosted list change reviews'), and the verb 'list' in the name reinforces the intent. It is distinct from the sibling get_change_review, which fetches a single review. However, the modifier 'hosted' and 'privacy-filtered project metadata' are vague and add little specificity, so it does not fully differentiate from other list tools like list_findings.

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?

No guidance is given on when to use this tool versus alternatives. The description does not mention conditions such as 'use this to list all change reviews for a project' or contrast with get_change_review for single-fetch. The agent must infer that listing is the purpose from the name, but there is no explicit direction on pagination, filtering, or 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.