email_outbound_filter

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only says 'settings,' which does not reveal whether the operation reads, writes, or affects anything. There is no mention of side effects, permissions, or whether this is a safe read-only operation.

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 text is short, but it is under-specified rather than concise. It omits the essential action or behavior, so brevity is achieved at the cost of usefulness.

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?

Although the tool is simple, zero-parameter, and has an output schema, the description still fails to state what the tool does. An agent cannot confidently choose between this and email_outbound_filter_update, making the definition 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?

The tool has zero parameters and 100% schema description coverage, so the schema has no parameter burden to carry. Baseline 4 is appropriate; the description does not need to add parameter meaning.

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, 'Outbound email filter settings,' is a noun phrase that essentially restates the tool name and provides no verb or action. It identifies the resource but does not say whether this tool gets, lists, or updates those settings, so it fails to distinguish itself even from the nearby email_outbound_filter_update sibling.

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 usage guidance is provided. The description does not state when to call this tool, when not to call it, or how it relates to email_outbound_filter_update or other email configuration tools.

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