list_pdfium_gerrit_cls

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It adds value by specifying the authentication requirement and hinting at the source ('PDFium dashboard'), but lacks details on rate limits, error handling, or output format. It doesn't contradict any annotations (none exist), but leaves gaps in behavioral context for a tool with authentication needs.

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 and includes essential context (authentication requirement). Every word earns its place with zero waste, making it easy for an agent to parse quickly.

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 no annotations and no output schema, the description is minimally complete for a listing tool with authentication. It covers the what and a key how (auth), but lacks details on output structure, error cases, or performance limits. For a tool with 3 parameters and authentication needs, this leaves the agent with incomplete operational context.

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 fully documents all three parameters. The description adds no additional parameter semantics beyond what's in the schema (e.g., it doesn't elaborate on query syntax or cookie format). This meets the baseline of 3 when the schema does the heavy lifting, 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 ('List') and resource ('PDFium Gerrit CLs from PDFium dashboard'), making the purpose immediately understandable. It distinguishes from siblings like 'list_gerrit_cls' by specifying 'PDFium' scope, though it doesn't explicitly contrast with other PDFium tools like 'get_pdfium_gerrit_cl_status'.

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 by mentioning 'requires authentication cookie', suggesting this tool is for authenticated access to PDFium Gerrit. However, it doesn't provide explicit guidance on when to use this versus alternatives like 'list_gerrit_cls' (general) or other PDFium-specific query tools, leaving the agent to infer based on the PDFium focus.

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