Replace Entries

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

Discloses max 50 entries, idempotency, matching by upsertBy, and deleteOrphans behavior. While annotations are absent, the description adds context beyond schema. Missing details on error handling or permissions but adequate given output schema existence.

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?

Three sentences with no redundancy. Key constraint (max 50) is front-loaded, followed by usage patterns and matching logic. Every sentence provides essential guidance.

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?

Covers main use case and batching strategy well. With 6 parameters, nested objects, and output schema, the description is comprehensive. Minor improvement: could explicitly state 'replace' action, but title suffices.

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?

With 100% schema coverage, baseline is 3. Description adds value by explaining batching strategy, deleteOrphans usage, and default upsertBy, enhancing semantic understanding beyond property descriptions.

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?

Explicitly states it performs idempotent sync of entries with optional orphan deletion. Distinguishes from siblings like delete-entries and set-entries by batching limit and deleteOrphans parameter.

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 guidance on when to use replace-entries vs alternatives (delete-entries + set-entries) and how to handle large catalogs with batching and deleteOrphans false/true pattern.

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