seed_add_documents

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It does not mention side effects, idempotency, whether existing rows are replaced or updated (though the schema mentions 'id' for updates), or any validation or permissions. The phrase 'exact payloads' hints at precision but fails to explain what happens on conflict or partial failure. This is a significant gap for a mutating tool.

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 exactly two sentences with no filler. The first sentence front-loads the core action, and the second provides usage context. Every word earns its place, and it is optimally sized for a simple tool.

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 provides a clear purpose and when-to-use guidance. The input schema covers all parameter semantics, and there is no output schema needing explanation. For a straightforward add-with-relations tool, this is nearly complete. The only missing piece is behavioral context (e.g., idempotency, conflict handling), which would elevate it to 5.

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 fully documents tableName, documents, id, fields, and relations. The description adds contextual meaning by specifying 'exact' payloads and 'when rows include relations,' which helps interpret the parameters, but it does not add new parameter-level details beyond what the schema already provides. 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 'Add exact Seed document payloads to a table,' which clearly identifies the verb (Add), the resource (Seed document payloads), and the target (a table). It also distinguishes itself from siblings by highlighting 'exact' payloads and the presence of relations, setting it apart from seed_add_mock_data and other tools.

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 second sentence, 'Use this when rows include relations,' provides explicit when-to-use guidance. It implies an alternative (likely seed_add_mock_data for mock data) without naming it explicitly, but the context signal from sibling tools makes the distinction clear. A slight improvement would be naming the alternative, but the guidance is functional.

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