prune_networks

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

No annotations provided, so description carries full burden. Discloses destructive nature and dry_run safety mechanism. However, lacks details on what 'unused' means, prerequisites, or side effects (e.g., does it affect Docker daemon?). Basic transparency but incomplete.

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?

Extremely concise: two sentences with no fluff. Purpose is front-loaded, critical safety info follows. Every sentence adds value.

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 destructive nature and 3 parameters, description covers primary purpose and safety but omits parameter details and output behavior (no output schema). Environment context (env_id) and confirmation mechanism are ambiguous. Adequate but not comprehensive.

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 has 0% description coverage. Description only addresses dry_run (with usage context). env_id and agent_token are not explained; their roles are unclear. Does not compensate for missing schema descriptions.

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?

Clearly states 'Prune unused Docker networks', specifying the verb (prune) and resource (Docker networks). Distinguishes from siblings like prune_images and prune_volumes by targeting networks.

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?

Provides usage guidance: mentions destructive nature, recommends dry_run=False for actual execution, and advises confirmation. Does not explicitly contrast with remove_network or other pruning tools, but the context of 'unused' aids selection.

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