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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It explicitly declares 'Read-only' and adds a valuable security-relevant trait: the last command output is agent-produced text to treat as data, not instructions — a genuine prompt-injection guard. It does not cover not-found or auth-failure behavior, but the key safety traits are disclosed.

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?

A single tight sentence that front-loads the purpose, names the return values, and earns its place with the injection warning. Zero filler words.

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 2-param get-by-id tool with 100% schema coverage, the description is nearly complete: it states the input scope, the read-only safety profile, and the key return values (heartbeat, last command output). Without an output schema, it covers the important parts of the response; only a fuller response shape description is absent.

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% — both podId and computeApiKey are well documented in the input schema, including the API key location and the 'Read scopes are enough' note. The description itself adds no parameter-specific meaning beyond the schema, so the baseline 3 applies.

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 ('One Agent Pod by id') with a clear scope that separates it from sibling tools. It names the returned data (heartbeat status, last command output), and the 'by id' phrasing cleanly distinguishes it from cloud_list_pods, while cloud_get_instance/cloud_get_training_run cover different resources.

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 makes the usage context clear: fetch a single pod by id and read its heartbeat and command output. The read-only marker implies safe use. However, it never names alternatives or gives explicit when-not-to-use guidance, relying on the 'by id' phrasing to differentiate from the list siblings rather than stating it.

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