AxKnowledgeBase_ingest_pdf_to_private_knowledge_base

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

With no annotations provided, the description carries the full behavioral burden and does so thoroughly. It discloses that the tool is synchronous and slow, idempotent for duplicate PDFs, requires an MCP elicitation confirmation before writing, and returns a plain non-error result without writing if confirmation is declined or unsupported.

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 dense but well-organized, with each paragraph serving a distinct purpose: scope and graph routing, timing and retry semantics, and elicitation behavior. Every sentence adds operational value, and the most important facts are front-loaded.

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?

Despite having no output schema, the description covers everything an agent needs to invoke this tool correctly: what it does, how long it takes, how to handle retries, what happens on user decline, and how clients without elicitation support behave. The failure semantics and idempotency guarantees are unusually complete.

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 100%, so the schema already fully documents file_path and doi. The description adds no parameter-specific nuance beyond what the schema provides, so the baseline 3 is appropriate.

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 states a specific verb and resource: ingest one local PDF into the organization's private knowledge graph. It also names concrete effects—parsing into passages, figures, tables, and references, plus storing the source PDF—and clearly differentiates this tool from the other write tool and from public-search siblings.

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?

It explicitly identifies the sibling delete tool, states that private-graph writes do not surface through search_knowledge_base, and gives actionable retry guidance: retry on timeout or unclear failure, but do not retry after decline, cancel, or unsupported elicitation. This gives the agent clear when-to-use and when-not-to-retry direction.

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