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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds real behavioral value beyond that: it discloses the response composition and a caveat that review threads stay at the git provider. It stops short of noting pagination, auth, or size limits.

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?

Two tightly packed sentences: verb+resource and the content list are front-loaded, followed by the call-for-action. Despite enumerating many items, no sentence is wasted.

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 carries the return-value burden and does so thoroughly, listing repositories, branches, commits, MRs, and hints. Nothing an agent needs to call this read-only tool correctly is missing.

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 both ID and key are already documented in the schema. The description adds nothing about identifier selection or syntax, so the baseline 3 for schema-fully-covered parameters applies.

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?

States a specific verb ('Returns') and resource ('a task's code') and then enumerates the exact contents: product repositories, live branches, commits with stats/paths, MRs, and reading hints. This clearly distinguishes it from siblings like task_context and feature_code_context.

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?

Provides an explicit usage scenario: 'when the user asks how a task is implemented or wants it reviewed.' Clear context for selecting the tool, but it names no alternatives or exclusions (e.g., task_context vs feature_code_context vs repo_context), so the routing is left partly to inference.

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