delete_wiki_node

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

With no annotations, the description carries full burden. It discloses the critical behavior that the underlying drive resource is not deleted, and explains the raw REST implementation due to missing SDK typing. It does not mention whether child nodes are recursively deleted or handle permission failures, which are relevant for a delete operation.

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?

Four sentences, front-loaded with the primary purpose. The technical note about UAT-first/bot fallback is an implementation detail that may not be needed for all users, but it's compact and valuable for an agent. Slightly verbose but well-structured.

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?

The description covers the most critical nuance (pointer vs resource deletion) and the necessary follow-up action, but lacks information about recursive deletion of children nodes, error behavior, or auth requirements. Given the moderate complexity and no output schema, it is not fully complete.

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?

Both parameters are fully described in the schema (100% coverage), so the baseline is 3. The description adds the endpoint template but does not provide additional syntax, formats, or constraints 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 explicitly states 'Delete a Wiki node' with the HTTP DELETE endpoint, clearly distinguishing it from sibling wiki operations like create/update/move/copy. It also clarifies the pointer semantics, making it clear that this tool only removes the wiki node, not the underlying drive resource.

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?

It provides clear context for the deletion operation and references `manage_drive_file` as a follow-up for deleting the actual resource, and suggests `get_wiki_node` to retrieve needed tokens. However, it does not explicitly state alternative scenarios (e.g., when to prefer managing the drive file directly), so it's clear but not exhaustive.

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