get_gerrit_cl_diff

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states the tool retrieves diff/changes but doesn't describe the return format (e.g., unified diff, JSON), pagination, rate limits, authentication needs, or error handling. For a tool with 3 parameters and no output schema, this leaves significant behavioral gaps, though it correctly indicates a read operation without contradiction.

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, efficient sentence that front-loads the core purpose ('Get the diff/changes for a Chromium Gerrit CL patchset') and ends with the specific goal ('to understand what code was modified'). There is zero waste, and every word earns its place, making it highly concise and well-structured.

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?

Given the tool has 3 parameters, no annotations, and no output schema, the description is incomplete. It lacks details on the return format, error conditions, rate limits, or how the diff is presented (e.g., text vs. structured data). For a tool that retrieves code changes, this omission is significant, as the agent won't know what to expect from the output.

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 the schema already documents all parameters thoroughly. The description adds no additional parameter semantics beyond what's in the schema (e.g., it doesn't explain format of the diff output or interactions between parameters). This meets the baseline of 3 when schema coverage is high, but doesn't compensate with extra insights.

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 clearly states the action ('Get the diff/changes') and resource ('for a Chromium Gerrit CL patchset'), with the specific purpose 'to understand what code was modified'. It distinguishes from siblings like get_gerrit_cl_status or get_gerrit_cl_comments by focusing on code changes rather than status or comments. However, it doesn't explicitly differentiate from get_pdfium_gerrit_cl_diff, which serves a similar purpose for a different codebase.

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 implies usage when needing to understand code modifications in a Chromium Gerrit CL, but doesn't provide explicit guidance on when to use this tool versus alternatives. For example, it doesn't mention when to choose this over get_gerrit_patchset_file (which might get specific file content) or search_chromium_commits (which searches across commits). The context is clear but lacks explicit alternatives or exclusions.

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