lattice_get_container

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

No annotations are provided, and the description describes a read-only operation ('Get full container details'). It does not mention any side effects, authentication requirements, rate limits, or other behavioral traits beyond the basic read nature.

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 that efficiently communicates the tool's purpose and scope, with no unnecessary 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?

Given the tool is a simple retrieval by ID with one parameter and no output schema, the description covers the essentials. It lists key details returned (config, health, env vars, ports), which is sufficient for an agent to understand the tool's scope.

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 100% coverage for the single parameter 'id' (description: 'Container ID'). The description does not add any additional semantic meaning beyond what the schema already provides, so baseline 3 is appropriate.

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 tool retrieves full container details including config, health, env vars, and ports. This distinguishes it from siblings like lattice_list_containers (list only) and lattice_get_container_logs (logs only).

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 usage when full container details are needed, but it does not explicitly state when not to use it or mention alternative tools for specific details (e.g., logs, metrics).

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