list_archived_instances

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

The readOnlyHint annotation already covers the safety profile, and the description's 'List' wording is consistent with a read-only operation. The description adds minimal behavioral detail beyond the annotation, such as no mention of pagination or empty-result behavior, but nothing contradicts the annotation.

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?

The description is a single, front-loaded sentence with no unnecessary wording. Every word contributes to understanding the tool's purpose and scope.

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 simple read-only list operation with no inputs, the description is sufficient to convey what the tool returns and for which resource. No output schema exists, but the description's 'List all archived sandbox instances' implies a list result; additional detail like pagination would be nice but is not critical for this simple tool.

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?

The input schema has a required 'input' wrapper object with no meaningful properties, so there are effectively no operation-specific parameters. The schema coverage is high, and the description does not need to explain parameters; it also does not add any parameter-related meaning.

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 the verb 'List' and the specific resource 'archived sandbox instances', which distinguishes it from the sibling list_instances tool. There is no ambiguity about what this tool does.

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 implies this tool is for archived instances, providing clear context for when to use it. It does not explicitly mention alternatives like list_instances for active instances, but the name and sibling list make the distinction easy to infer.

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