build_pdf_knowledge_db

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

No annotations provided, so description carries full burden. It mentions local model and no API key, but does not disclose side effects like whether existing data is overwritten, performance implications, or error cases. The force_rebuild parameter hints at behavior but lacks detail.

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 fairly concise with a logical structure: purpose, model info, database convention, then parameter descriptions. It could be slightly shorter by removing the model details if not critical, but overall efficient.

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 an output schema exists (not shown), description need not explain returns. However, it lacks details on prerequisites (database must exist), error handling, or success indicators. For a tool with no annotations, more completeness is needed.

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 description must add value. It explains 'database' is a slug with examples and 'force_rebuild' means re-indexing already indexed files. This provides useful context beyond the schema definitions.

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 indexes PDFs into a semantic knowledge base using a specific model. It distinguishes itself from siblings like 'create_knowledge_database' which creates the layer, and 'search_pdf_knowledge' which queries. Examples of database slugs further clarify the purpose.

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 implies the database must exist (created via create_knowledge_database()), but gives no explicit guidance on when to use this tool vs alternatives like index_library_pdfs. No mention of prerequisites or when to set force_rebuild.

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