sieve_script_create

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

With no annotations, the description carries full burden. It only mentions the credential requirement, but does not disclose what happens on success, whether it overwrites existing scripts, any side effects, or the response format. This is a meaningful gap for a creation tool.

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 two concise sentences, front-loaded with the primary action and resource. Every word earns its place, with no redundancy.

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?

For a create tool, the description is minimally adequate but would benefit from clarifying the distinction from domain_sieve_create and the dependency on alias_generate_password. The schema fills in parameter details, but the lack of any note about interaction with other tools (e.g., activation) leaves some context incomplete.

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 100%, so the baseline is 3. The description adds only the context that alias_username and alias_password are 'credentials,' but this is already implied by the schema's required fields and descriptions (e.g., 'Alias password from the alias_generate_password tool'). No extra meaning is provided.

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 a specific verb and resource: 'Create a Sieve script for an alias.' This distinguishes it from sibling tools like domain_sieve_create (which targets domain-level scripts) and other sieve_script_* tools (update/delete/activate).

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 phrase 'for an alias' clearly indicates the intended use case, and 'Requires alias credentials' provides a necessary prerequisite. While no alternatives are explicitly named, the context is unambiguous enough to differentiate from domain-level operations.

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