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

Annotations already mark this destructive, but the description adds substantial context: cloud sync to Drive trash, pointer files removing real documents, refusal to delete non-empty folders, and the two-step preview/confirm flow. This goes well beyond the annotations and schema.

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 carrying essential information: the core action, notable edge cases, and the confirmation workflow. No filler or redundant restatement of the tool name.

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 destructive nature, cloud sync implications, folder-content limitation, pointer behavior, and the required confirm step. With an output schema present, this is complete enough for an agent to invoke the tool correctly and safely.

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 both parameters already have clear descriptions. The description adds meaningful operational detail by explaining that the first call is a preview and confirm=true is the actual deletion trigger, reinforcing the schema's 'Must be true' note.

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 opens with a specific verb and resource: 'Deletes a file or an empty folder from the synced Google Drive folder.' It also clarifies non-obvious behavior (pointer files deleting the real Google Doc) and distinguishes this from generic file deletion by scoping it to the Google Drive mount.

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 clearly states when deletion is allowed (file or empty folder) and when it is not (folders with contents). It does not explicitly name an alternative tool, but the Google Drive scope and the preview/confirm workflow make appropriate usage evident.

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