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

Annotations already declare destructiveHint=true and non-idempotence, so the safety profile is covered; the description adds real value by disclosing that removeArchive deletes the archive within the same call, not as a separate step. It still omits what happens to pre-existing files at the destination (overwrite vs fail) and any permission requirements, which matter for a destructive 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?

Two sentences, front-loaded with the core action, with no filler. The second sentence is slightly roundabout but earns its place by explaining the flag's side effect.

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?

Incorrect for this tool: with three required but fully undocumented parameters, an ambiguous "in place" destination, no output schema, and a destructive extraction, an agent lacks what it needs to call this safely. The definition should at minimum identify what id, file, and root refer to.

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 0% for four parameters, so the description carries the full burden, yet it only clarifies removeArchive's timing. The three required parameters (id, file, root) are never explained, and root's "/" default leaves the extraction target ambiguous.

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?

"Decompress an archive in place" states a specific verb and resource, which cleanly separates it from files_compress. The scope qualifier "in place" is not defined (extract next to the archive? into the given root?), so the agent still has to guess the destination semantics before calling.

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 supplies one narrow scenario ("an upload-and-unpack never leaves the archive behind") but never says when to choose this tool over alternatives such as reading or downloading the archive, nor what prerequisites must hold before decompressing. There are no explicit when-not conditions.

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