delete_wiki_node

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

With no annotations, description fully discloses that the underlying drive resource is NOT deleted, explaining pointer semantics. It also mentions SDK limitation (untyped endpoint) and fallback mechanism. This provides complete behavioral transparency.

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, each valuable: purpose, API details, behavioral clarification. Well-structured with front-loaded purpose. No fluff.

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 no output schema, description adequately explains outcome (pointer deletion only) and provides follow-up instructions. Also mentions API version and SDK specifics, making it contextually complete for safe and correct usage.

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% and description lists space_id and node_token as in schema, but adds no extra meaning beyond the schema descriptions. Baseline 3 is appropriate.

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 it deletes a Wiki node, using specific verb 'Delete' and resource 'Wiki node'. It distinguishes from deleting the underlying drive resource, and siblings like create_wiki_node, copy_wiki_node, move_wiki_node, update_wiki_node, get_wiki_node are present, so purpose is clear and differentiated.

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 (delete wiki node) and when not to rely on it for underlying resource deletion. Provides clear follow-up action with manage_drive_file, and alternative to get_wiki_node first. Also mentions the API endpoint and SDK behavior.

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