veritasgraph_ingest_document

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

The description discloses key behavioral traits: chunking, extraction with a local model, and attribution. Since annotations are absent, the description carries the full burden, and it provides reasonable insight into the tool's operation. However, it does not mention side effects like graph mutation, performance implications, or error handling.

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 with two sentences. The first sentence states the core purpose, and the second elaborates on the process. No extraneous information; every sentence adds value.

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?

The description covers the input and process but omits output/return value, error conditions, or performance considerations. Given the tool's complexity and no output schema, more details would improve completeness.

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 coverage is 100% with clear parameter descriptions. The description adds context on how 'text' is processed (chunking, extraction) but does not add significant meaning beyond the schema for 'model' or 'title'. Baseline 3 is appropriate as the schema does the heavy lifting.

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 verb 'ingest' and the resource 'document into the VeritasGraph knowledge graph'. It details the process (chunks text, extracts entities and relationships, records source chunk for attribution), which is specific and distinguishes this tool from siblings like clear_graph, get_graph, query, and search_entities.

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 what the tool does but does not explicitly state when to use it over siblings. There is no mention of when not to use it or alternatives. The usage is implied through the description, but no direct guidance is given.

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