eap_fix_pdf

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

No annotations provided, so description carries full burden. Discloses actions, return format (24h URL with zip), and cost. Missing details on failure modes, whether original PDF is unchanged, and auth requirements.

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?

Description is concise with three sentences, front-loading the purpose. Includes relevant billing info. No unnecessary verbiage.

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?

Covers input (URL), process (auto-fix, re-audit), output (zip with three files), and constraints (cost, 24h URL). Lacks details on error handling but is sufficient given no output schema.

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 coverage is 100% with descriptions for both url and title. Description adds only the 'publicly accessible' constraint for url, which is already in schema. No significant extra meaning.

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?

Clearly states the tool auto-fixes PDFs for accessibility, listing specific actions (inject metadata, auto-tag, re-audit). Distinguishes from siblings like eap_check_pdf (check only) and eap_convert_to_markdown (conversion).

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?

States cost and that membership does not include auto-fix, and requires a publicly accessible URL. Does not explicitly say when to use or not, but purpose is clear enough to infer.

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