pdfops_usage

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 conveys a read-only check ('Check the current... quota') and discloses the authentication requirement ('Requires PDFOPS_API_KEY'). It also previews the response fields, giving the agent useful expectations without relying on an output schema.

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 sentence with no filler. It front-loads the core action and resource, adds the returned fields, and ends with the essential prerequisite. Every part earns its place.

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?

This is a simple no-parameter tool with no annotations or output schema. The description fully covers what the tool does, what it returns, and the required environment variable. Nothing essential is missing for an agent to select and invoke it correctly.

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?

There are zero parameters, so the schema provides no meaningful semantics to augment. The description correctly focuses on the configured key and the quota values returned, which is the relevant context for a parameterless tool.

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 names a specific verb and resource: 'Check the current PDFops API quota for the configured key.' It also enumerates the exact data returned (tier, limit, used, remaining, reset date), which clearly distinguishes this quota-checking tool from the sibling PDF-processing tools like pdf_fill and pdf_merge.

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 clearly states that this tool is for checking API quota, which is a distinct purpose among the siblings. It does not explicitly name alternative tools or state when not to use it, but the 'quota' concept makes the intended usage unambiguous.

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