noteker_process_pdf

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

The description discloses key behavioral traits: batching (max 5 pages per batch), sequential processing across batches, single combined Markdown output, and the optional 'note_context' parameter to aid resolution. The 'readOnlyHint' annotation is not contradicted as the tool does not modify input files. Slightly more detail on the max_pages cap could improve, but it's well-covered.

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 and well-structured, using bullet points for parameters and separate sentences for behavior. It delivers all necessary information without fluff, earning its space with every sentence.

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's complexity (4 parameters, batching logic, output schema exists), the description covers all input aspects and processing behavior clearly. The presence of an output schema reduces the need to describe return values, and the description mentions the final result is a single combined Markdown document, making it complete for an agent to invoke 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?

Despite 0% schema description coverage, the description provides thorough explanations for all four parameters: file_path (absolute path), note_context (hint for ambiguous words), page_start (1-based inclusive, default 1), and page_end (inclusive, default last page with cap). It also explains batching behavior, adding significant meaning beyond the schema.

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 tool name 'noteker_process_pdf' and description clearly state its function: converting local PDFs of handwritten notes into Markdown using Claude Vision. The verb 'Convert' and resource 'local PDF' are specific, and it implicitly distinguishes itself from the sibling 'noteker_status' which presumably checks 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 explains when to use it (for converting handwritten note PDFs) and provides contextual details like batching behavior and page range handling. It does not explicitly state when not to use it, but the sibling tool 'noteker_status' suggests a clear divide, making usage context adequate.

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