quire.deleteDocument

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

The description adds 'This action cannot be undone', but the annotations already include destructiveHint: true, so the added value is minimal. No other behavioral details (e.g., authorization, side effects) are disclosed beyond the annotations.

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 two sentences with no wasted words. It front-loads the action and optional methods, and includes critical irreversibility information. Every sentence contributes meaning.

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 tool has 4 parameters with full schema coverage, no output schema, and annotations indicating destructiveness, the description covers the key aspects: deletion methods and irreversibility. It does not describe return values or effects, but these are less critical for a delete operation.

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 already documents all parameters. The description provides a high-level summary of the two parameter groups (OID vs ownerType+ownerId+documentId) but adds no new semantic detail beyond the schema.

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 verb 'Delete' and resource 'document', and distinguishes between two identification methods (OID vs ownerType+ownerId+documentId). It also notes irreversibility. Sibling tools like deleteChat, deleteComment confirm the tool is distinct.

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 description explains when to use OID versus ownerType+ownerId+documentId, providing clear context. However, it does not explicitly state when not to use this tool or mention alternatives among siblings.

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