lattice_get_worker_container_stats

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

With no annotations provided, the description carries full burden. 'Get' suggests a read operation, and 'live' implies real-time data, but no details on latency, data freshness, or behavior when the worker is unreachable. The description lacks disclosure of any observational or safety traits.

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 sentence of 9 words, no filler or repetition. Every word is functional, making it highly efficient for an AI agent to process.

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?

The tool has a single parameter and no output schema. The description does not compensate for the missing output schema by hinting at the return format or types of stats (e.g., CPU, memory). An agent lacks sufficient context to interpret the tool's response, reducing completeness.

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 one parameter 'id' described as 'Worker ID'. The description adds 'from one worker' but does not provide additional meaning beyond the schema. Per guidelines, baseline 3 is appropriate when schema coverage is high.

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?

Description clearly states the verb 'Get' and the resource 'live per-container resource stats from one worker'. It distinguishes from sibling tools like lattice_get_worker (worker info) and lattice_get_worker_metrics (aggregate metrics) by specifying per-container scope and 'live' data.

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?

Description implies usage for retrieving container resource stats from a specific worker but provides no explicit guidance on when to use this tool over alternatives such as lattice_get_container_metrics or lattice_get_worker_metrics. No prerequisites or exclusions are mentioned.

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