AxKnowledgeBase_search_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 burden of behavioral disclosure. It states that results are the most similar passages, each with its source paper for citation, and explains the default graph-wide search behavior plus the self_only restriction. This provides meaningful behavioral context, though it does not mention edge cases like empty results or pagination.

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 compact and well-structured. It front-loads the core purpose, immediately contrasts the tool with its sibling, and then clearly explains the default scope and the self_only variant. Every sentence adds meaningful information with no fluff.

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?

For a 3-param tool with no output schema, the description adequately covers purpose, usage, return shape (most similar passages with source paper), and default behavior. It could add a bit more detail about how limit is applied or what happens when no results are found, but these are minor gaps given the overall clarity.

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 baseline is 3. The description adds value beyond the schema by explaining the real-world meaning of self_only: the default searches every paper in the organization's private graph regardless of ingester, while setting self_only=True limits results to the caller's own papers. This contextualizes the parameter semantically.

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 opens with a specific verb and resource: 'Semantic search over the organization's private knowledge base'. It explicitly distinguishes this tool from Axiomatic's curated corpus and names the sibling search_knowledge_base as the alternative, so an agent can immediately tell them apart.

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 gives explicit when-to-use guidance: 'Use this to find anything ingested with ingest_pdf_to_private_knowledge_base; use search_knowledge_base for the curated corpus.' It further clarifies the default broad scope and the self_only=True restriction, providing complete routing and selection context.

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