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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the mutation-but-non-destructive profile is covered. The description adds the 100-file-per-call batch ceiling, but that same limit is repeated in the file_ids schema, and it says nothing about permission requirements, partial failures, or what happens to files beyond the cap.

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 sentences with the core action front-loaded and the prerequisite second. The trailing sentence 'The answer lists every file on its own' is slightly awkward and adds marginal parsing guidance rather than substantive information.

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 4-parameter, single-required-field mutation with full schema coverage and no output schema, the description covers purpose, prerequisite and batch limit adequately. It omits error/partial-success behavior and permissions, which would help but are not strictly required here.

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%, so person, project, dry_run and file_ids are already documented. The description restates the id-passing and the 100 cap already present in the schema and adds no new meaning for person, project, or dry_run. Baseline 3 applies when the schema does the heavy lifting.

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 ('Take files or folders back out of the connected Google Drive's Trash') rather than restating the tool name, and distinguishes the operation from trashing by naming the inverse sibling workflow (trash_google_drive_files). An agent can tell this is the un-trash operation without opening the schema.

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?

Gives clear sequencing guidance — pass the ids returned by the trash_google_drive_files answer — so the agent knows this follows a trash-listing call. It does not explicitly state when NOT to use it (e.g. versus connections_storage_restore_from_trash), which keeps it below a 5.

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