add_email_filter

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

With no annotations present, the description carries the full disclosure burden. It does add one genuinely useful behavioral detail — that cPanel ignores the final rule's opt field — but it says nothing about authentication needs, validation failures, or what happens to a filter with a duplicate name beyond what the schema already states.

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?

Two sentences, no filler, and the core action is front-loaded. The cPanel quirk is placed second where it belongs, so the definition is efficient and well-ordered.

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 four-parameter mutation tool with no annotations and no output schema, the definition is thin. The schema covers the parameter shapes well, but the description should say the filter is live immediately, whether login is required, and what a successful result looks like.

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 earns that baseline by clarifying how rules join, but the per-rule opt semantics are already documented in the schema, so the only marginal addition is the note that the last opt is ignored.

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 opens with a specific verb and resource: "Create or update an email filter." That is enough to separate it from list_email_filters, delete_email_filter, and trace_email_filter in the sibling set, even though none of those are named explicitly.

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?

There is no guidance on when to choose this tool over its siblings, no mention of prerequisites such as an authenticated cPanel session, and no note that an existing filter must be removed rather than edited. The agent has to infer all of that from the name alone.

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