scrape_pdf

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

With no annotations, the description should fully disclose behavior. It mentions extraction and skill building but omits details on side effects, persistence, or required permissions. The phrase 'build Claude skill' is vague and does not explain the output or system changes.

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 concise with only two sentences, but it omits critical information about parameters and output. Conciseness should not sacrifice completeness; this is underspecified rather than efficiently detailed.

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 five optional parameters, no schema descriptions, and an output schema without explanation, the description is incomplete. It does not specify which parameter provides the PDF path or what the output contains, leaving the agent to guess.

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?

Input schema coverage is 0% with no parameter descriptions. The description does not clarify the purpose of any of the five optional parameters (config_path, pdf_path, name, description, from_json). Tools with multiple optional parameters require explanation of their roles.

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 scrapes PDF documentation and builds a Claude skill, specifying it extracts text, code, and images. This distinguishes it from sibling scrape tools targeting other sources like codebases, videos, or generic content.

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?

No guidance is provided on when to use this tool versus alternatives like scrape_docs or scrape_generic. The description lacks context about prerequisites or scenarios where a different tool would be more appropriate.

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