Validate Import

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

No annotations provided, but the description covers behavioral traits: it is a dry-run ('without writing'), checks duplicate upsert keys and unknown moduleName refs, and enforces a max 50 entries. This fully informs the agent of what the tool does and does not do.

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, front-loaded with the core purpose, and every sentence provides essential guidance. No unnecessary words or repetition.

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 the output schema exists (context signal), the description does not need to explain return values. It adequately covers purpose, usage, parameter behavior, and constraints, making it complete for the agent to invoke correctly.

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%, so baseline is 3. The description adds context by linking parameters to behavior (e.g., 'Checks duplicate upsert keys' relates to checkDuplicates, 'unknown moduleName refs' to checkModuleExists) and by noting the max 50 entries, which corresponds to the entries array maxItems.

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 performs 'dry-run validation for a proposed import batch (max 50 entries)', specifying the verb (validate), resource (import batch), and scope (dry-run, max 50). It distinguishes from sibling tools like set-entries and replace-entries by emphasizing no writing.

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?

Provides explicit when-to-use (before actual import) and alternatives: 'For full re-import: delete-entries once, then set-entries in 50-entry chunks; or replace-entries with deleteOrphans=false until the final batch (deleteOrphans=true).' Also advises splitting large catalogs into batches of ~50 to avoid oversized payloads.

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