bulk_delete_kb_docs

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is known; the description's 'Destructive and irreversible' mostly restates that, though 'irreversible' adds a nuance beyond the hint. It says nothing about partial-failure behavior, batch limits, or required permissions, which matter for a bulk destructive call.

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 short clauses: action, endpoint, alternative preference. Nothing is wasted and the destructive warning is not buried.

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?

For a destructive bulk operation with no output schema and zero parameter documentation, the definition covers the essentials (what it does, that it is irreversible, which sibling it replaces) but omits batch size limits, partial-success semantics, and auth requirements an agent would want before firing it.

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 0%, so the schema gives only names and types for docIds and agentId. The description adds no semantics for either — no mention of what agentId scopes, whether all docIds must belong to it, or how missing/invalid IDs are handled.

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?

States a specific verb and resource with its bulk scope ('Delete many KB documents in one call') and even names the endpoint. It is immediately distinguishable from the singular delete_kb_doc sibling.

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?

'Prefer over looping delete_kb_doc' explicitly names the alternative and the condition that selects this tool. It does not state any when-not cases (e.g. single-doc deletion threshold or size limits), so it falls short of a 5.

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