get_docker_info

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

With no annotations, the description must fully disclose behavioral traits. It only states 'Get Docker system information,' which is vague. It does not confirm whether the operation is read-only, whether authentication is needed, or what side effects (if any) occur. The description lacks sufficient clarity for safe agent invocation.

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 sentence, which is concise. However, it achieves conciseness at the expense of completeness. It is well-structured but lacks necessary details, so it does not earn its place fully.

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's simplicity (2 optional params, no output schema), the description should still clarify what 'system information' includes. It fails to do so, leaving the agent without enough context to interpret results or handle parameters. The description is incomplete for operational use.

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 description coverage is 0%, and the description does not explain any parameter. The two parameters (env_id and agent_token) are described only by their schema defaults. The description adds zero value in clarifying their purpose or format, leaving the agent to guess.

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 Docker system information for a given environment. It uses a specific verb ('Get') and resource ('Docker system information'), making the purpose straightforward. However, it does not explicitly distinguish from similar sibling tools like get_system_health or get_docker_version.

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?

No guidance is provided on when to use this tool versus alternatives. There is no mention of context, prerequisites, or situations where another tool would be more appropriate. The description is silent on usage scenarios.

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