stalwart_list_sieve_scripts

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

There are no annotations, so the description carries the burden. 'List' clearly implies a read operation, but it does not disclose potential nuances such as whether scripts are returned by name only, ordering, pagination, or permission requirements. The simple verb provides baseline transparency but lacks richer behavioral context.

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 a single concise sentence with no fluff. It is appropriately brief for a simple list operation, though it could benefit from a bit more contextual detail without becoming verbose.

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 the tool's simplicity and the presence of an output schema, the description covers the basic purpose but lacks usage guidance and context about when to use it versus sibling tools. It is minimally viable but leaves gaps in situational understanding.

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?

The schema has 0% parameter description coverage and the tool description does not explicitly explain the account_id parameter. The phrase 'of an account' loosely implies it, and the parameter name is self-explanatory, but the description adds minimal value beyond the schema's existing 'account_id' title.

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 'List Sieve filter scripts of an account' uses a specific verb and resource, clearly distinguishes this from sibling tools like list_domains or list_identities, and specifies the scope (per account).

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?

No guidance is provided on when to use this tool versus alternatives. It does not mention appropriate contexts, prerequisites, or exclusions, leaving users to infer that it is the tool for Sieve scripts.

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