set_network_policy

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

No annotations provided; description lacks disclosure of side effects (e.g., impact on active operations, persistence, privilege requirements). A system-wide network policy change could have significant consequences, but no warnings are given.

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 with front-loaded purpose, followed by clear bullet-like explanations of policy options. No redundant information.

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 annotations and only one parameter, description covers purpose, argument semantics, and policy meanings. Missing mention of return value (output schema exists) and whether change is immediate/persistent, but overall adequate.

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 no description for 'policy' (0% coverage); description fully compensates by listing valid values and explaining each one, providing essential semantics for correct usage.

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 'Set the current network access policy for all agents' with specific verb and resource. Lists three distinct policy options, distinguishing from sibling 'get_network_policy'.

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?

Describes when to use each policy option ('No internet access', 'Default', 'Airplane mode') but does not explicitly state when not to use the tool or mention alternatives beyond implied get tool.

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