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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is fully covered. The only added signal is 'privacy-filtered project metadata', which hints at a data-trimming behavior but is too vague to disclose what is filtered or what the response contains.

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?

It is a single sentence, so it is short, but 'Read hosted get change review' is awkward and wastes its opening on redundant/ungrammatical phrasing instead of front-loading the actual behavior.

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 annotations, no output schema, and four parameters, the description should at minimum say what a change review is, how a reviewId is obtained, and how it differs from the list sibling. None of that is present, leaving the agent under-informed.

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 coverage is nominally 100%, but all four parameters (reviewId, projectId, sessionId, executionId) carry the identical copy-pasted description 'Owned project ID returned by list_linked_projects', which is factually wrong for reviewId/sessionId/executionId. The description adds nothing about parameters, so it fails to compensate for that misleading schema text.

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 phrase 'get change review' names a recognizable verb+resource, but the surrounding text ('Read hosted ... using privacy-filtered project metadata') is garbled filler that muddles rather than sharpens the purpose. It gives no differentiation from close siblings like list_change_reviews or create_local_change_review, which an agent must choose between.

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 versus list_change_reviews, refresh_local_change_review, or any other review-related sibling. The agent gets no trigger conditions or prerequisites (e.g., that a reviewId first comes from list_change_reviews).

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