network_prune

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

Description adds context beyond annotations: built-in networks are safe, only zero-connected networks eligible, filter details. Annotations indicate destructive and idempotent; description reinforces that.

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?

Description is concise and well-structured with bullet points for filter keys and clear separation of usage advice, though minor redundancy could be trimmed.

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 no output schema, description provides return format. Covers eligibility, built-in networks, filters, and alternatives. Highly complete for a pruning tool.

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 for the only parameter 'filters'. Description details valid filter keys (`until`, `label`) and semantics of omission, adding significant value.

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 'Remove networks that have no active container endpoints.' It distinguishes from sibling tool 'network_remove' and specifies that built-in networks are never removed, providing a specific verb+resource.

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?

Explicitly tells when to use (remove unused networks) and when not (use network_remove for specific networks). Also explains filter usage and omission behavior.

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