get_pdfium_gerrit_cl_diff

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool retrieves diffs but doesn't mention critical details like whether it's a read-only operation, potential rate limits, authentication needs, or what the output format looks like (e.g., raw diff text, structured data). For a tool with no annotations, this leaves significant gaps in understanding its behavior and constraints.

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, well-structured sentence that efficiently conveys the tool's purpose without unnecessary words. It's front-loaded with the core action ('Get the diff/changes') and includes the rationale ('to understand what code was modified'), making it easy to parse. Every part of the sentence earns its place, resulting in an optimal balance of clarity and brevity.

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's moderate complexity (3 parameters, no output schema, no annotations), the description is adequate but incomplete. It explains what the tool does but lacks details on behavioral aspects (e.g., safety, output format) and doesn't leverage context from siblings. For a tool focused on code analysis, more guidance on usage scenarios or output interpretation would enhance completeness, but it meets the minimum viable threshold.

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?

The input schema has 100% description coverage, clearly documenting all three parameters (cl_number, patchset, file_path) with their types and optionality. The description adds no additional parameter semantics beyond what's in the schema, such as format examples or usage tips. With high schema coverage, the baseline score of 3 is appropriate, as the schema does the heavy lifting.

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 tool's purpose: 'Get the diff/changes for a PDFium Gerrit CL patchset to understand what code was modified.' It specifies the verb ('get'), resource ('diff/changes'), and scope ('PDFium Gerrit CL patchset'), making it easy to understand what the tool does. However, it doesn't explicitly differentiate from sibling tools like 'get_gerrit_cl_diff' or 'get_pdfium_gerrit_patchset_file', which is why it doesn't reach a perfect score.

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 context ('to understand what code was modified'), suggesting it's for analyzing code changes. However, it doesn't provide explicit guidance on when to use this tool versus alternatives like 'get_gerrit_cl_diff' (for non-PDFium Gerrit) or 'get_pdfium_gerrit_patchset_file' (for specific file content). The usage is clear but lacks sibling differentiation and exclusions.

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