zen_set_policy

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

No annotations are provided, so the description carries the burden. It explains that read-only mode blocks write actions while allowing read ops, which is helpful. However, it does not disclose whether setting policy overwrites existing policies, or if there are any side effects, leaving some behavioral aspects unclear.

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 three sentences, front-loaded with the main purpose, then explains read-only mode succinctly, and ends with a usage note. 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 three optional parameters, no output schema, and simple function, the description covers the purpose of each parameter and provides a use case. It lacks mention of default behavior or cumulative effects, but is reasonably complete for a straightforward setting 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 description coverage is 0%, so the description must add meaning. It maps parameters to 'allow/deny regex lists' and 'read-only mode', providing essential context beyond the bare parameter names. While it doesn't specify regex format or that allow/deny are arrays, it adds 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 the tool's action ('Set') and the resources ('URL allow/deny regex lists' and 'read-only mode'). It is concise and distinct from siblings, as no other sibling tool appears to set 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?

The description provides a use case for read-only mode ('useful for let the agent observe only'), but does not explicitly state when to use this tool over alternatives or when not to use it. It implies usage context but lacks explicit guidance.

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