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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds 'privacy-filtered project metadata,' which hints at data filtering, but this is vague and unexplained. No other behavioral details (e.g., what is filtered, response format, error cases) are provided.

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, so it is concise in length, but the wording is awkward ('hosted get change review') and not front-loaded with the most useful information. It lacks clarity despite being short.

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 tool with two required parameters and no output schema, the description provides minimal context. It does not explain what a 'change review' is, what 'privacy-filtered' means, or what the return value looks like. The description is inadequate for an agent to understand the tool's full behavior.

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%, and the description does not explain any of the four parameters. It does not clarify what projectId, reviewId, sessionId, or executionId mean or how they relate to the operation. The description entirely fails to compensate for the lack of schema descriptions.

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 verb ('Read') and a resource ('hosted change review'), which gives some sense of purpose. However, the phrasing 'hosted get change review' is awkward and could be misread. It does not explicitly distinguish from siblings like list_change_reviews or refresh_local_change_review beyond implying a hosted vs local distinction, which is not stated clearly.

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 guidance on when to use this tool versus alternatives. Siblings like list_change_reviews, create_local_change_review, and refresh_local_change_review exist, but the description gives no criteria for selecting this tool over them. The agent must infer from the name alone.

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