parse_pdf_structure

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

With no annotations, the description must carry full behavioral burden. It discloses that it creates a background job (implying async), but does not reveal safety, side effects, or what the job does in detail. The reader cannot tell if this is read-only, what gets modified, or what the output represents.

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 under-specified sentence. It is not concise in a helpful way—it omits critical details. The low word count is not efficient but insufficient.

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 10 parameters, no annotations, and an output schema, the description is grossly incomplete. It does not describe what the parsed structure is, how the job works, what the output semantics are, or when to choose this over linked tools. The description is almost entirely inadequate.

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% and the description provides no parameter information. It mentions 'configured structured PDF extractor' but does not explain any of the 10 parameters (e.g., ocr_enabled, page_ranges, deskew). The description fails to add 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 description mentions 'structured PDF extractor' and 'background job' which hints at parsing PDFs, but the primary verb is 'Create a background job', which is vague and doesn't explicitly state it parses PDF structure. It does not differentiate from sibling tools like ingest_documents or convert_document.

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 on when to use this tool versus alternatives. The description lacks any context about prerequisites, scenarios, or exclusions. It is a single statement with no usage context.

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