Get Sandbox Metrics

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

The description adds the context of 'live' metrics, but annotations already indicate read-only and idempotent behavior; no significant additional behavioral disclosure beyond annotations.

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 concise sentence of 13 words, front-loaded with the key action and resource, with no unnecessary details.

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?

Given the simple input schema (one required param) and no output schema, the description adequately lists the types of metrics returned, though it omits format or granularity.

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% with a single 'name' parameter described as 'Sandbox name'; the description adds no extra semantic value beyond what the schema provides.

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 'Get' and the resource 'live resource usage metrics (CPU, memory, disk, network)' for a running sandbox, distinguishing it from sibling tools like sandbox_inspect.

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 the tool is for monitoring a sandbox's real-time metrics but does not explicitly state when to use it or provide alternatives like sandbox_inspect for status details.

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