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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the "Read-only" sentence is largely restating structured data; the extra detail is the host-level note that the server marks it read-only and it therefore runs immediately. Nothing is said about pagination, ordering, result limits, or what happens with large quarantines, which are the remaining behavioral questions an agent would have.

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?

Front-loaded with the core action, and the long field list is genuinely informative rather than filler. The trailing 'Through Royally' sentence is slightly cryptic and could be tighter, but overall there is little waste.

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?

With no output schema, the field enumeration is exactly what an agent needs to know what comes back, and the read-only framing is covered. Gaps remain around result volume, ordering, and cost of listing, but for a 2-param read-only tool it is close to 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?

Schema coverage is 100% and both parameters (status enum, site_id enum) carry their own descriptions, so the parameter burden is already met. The description only obliquely touches the status filter via "whether it was restored" and adds no format, default, or combination guidance beyond the schema — baseline 3.

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?

Specific verb + resource ("List files and folders moved into quarantine") plus an enumeration of the returned fields (id, original path, size, sha256, reason, restored status), which makes the tool's scope unambiguous. It does not, however, distinguish itself from the many other list/get tools in the sibling set beyond naming the companion quarantine-file tool.

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?

Usage is implied rather than stated: the agent can infer this is the inspection tool for the quarantine area, and the "Read-only ... so it runs straight away" line hints there is no approval gate. There is no explicit when-to-use versus alternatives, no prerequisite/permission note, and no guidance on when to pick this over a general file-listing tool.

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