Paper Pilot

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

No annotations are provided, so the description carries the full burden. It mentions saving a text sidecar and returning top matching chunks, which adds some behavioral context. However, it lacks details on permissions needed, error handling (e.g., invalid PDFs), rate limits, or what 'matching chunks' means in practice (e.g., relevance to 'research_question'). For a tool with 6 parameters and no annotations, this is insufficient.

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 key actions (extract, save, return). There's no wasted wording, but it could be more structured (e.g., separating primary and secondary functions). It appropriately conveys the core purpose without redundancy.

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 complexity (6 parameters, no annotations, no output schema), the description is incomplete. It doesn't explain the tool's output format, error conditions, or how parameters interact (e.g., 'research_question' influencing 'top_chunks'). For a tool that performs multiple operations (extraction, saving, chunking), more detail is needed to guide effective use.

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 0%, so the schema provides no parameter details. The description mentions 'top matching chunks' and implies text extraction, but doesn't explain any parameters (e.g., what 'title_hint' or 'research_question' do, how 'chunk_size_chars' affects output). It fails to compensate for the low schema coverage, leaving most parameters undocumented.

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: extracting text from a local PDF, saving a sidecar file, and returning matching chunks. It specifies the resource (local PDF) and actions (extract, save, return chunks). However, it doesn't explicitly differentiate from siblings like 'render_pdf_pages' or 'inspect_open_access_pdf', which may also handle PDFs but with different functions.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., file accessibility), exclusions (e.g., encrypted PDFs), or compare to sibling tools like 'deep_read_topic' or 'research_topic' that might involve text analysis. Usage is implied only by the tool name and description.

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