Delete Entries

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

No annotations provided, so description carries full burden. It discloses destructive nature via 'delete' and safety guard (confirm). However, it does not mention irreversibility, cascading effects, or permission requirements. Still, it provides adequate transparency for an agent to understand the operation's gravity.

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, front-loaded with core action, then required flag, then usage guidance. Every sentence adds value without redundancy.

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 complexity of a bulk delete with filters and the presence of an output schema, the description is fairly complete. It covers purpose, required parameter, alternatives, and context. Minor lack of behavioral depth (e.g., irreversibility) keeps it from a 5, but it's sufficient.

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. Description adds minimal extra meaning beyond schema—it mentions the filter criteria but does not elaborate on nuances like the relationship between 'kind' and 'kinds' or the role of 'confirm' beyond 'must be true'. Hence, at baseline.

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?

Description clearly states it bulk deletes entries matching a filter by kind/moduleName/tags. It distinguishes from siblings like delete-entry (singular) and delete-module/delete-slice by specifying bulk operation and filter criteria.

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?

Explicitly states when to use (before full re-import, to clear a module slice) and when not to (prefer replace-entries with deleteOrphans for idempotent sync). Also notes confirm=true requirement.

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