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

With no annotations, the description carries the burden of behavioral disclosure. It explicitly states that rules react to events with configurable actions, which adds useful context about the resource itself. However, it does not disclose behaviors like pagination, ordering, default filter behavior when 'enabled' is omitted, or the response format. For a read-only list tool, this is adequate but not rich.

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 concise sentences. The first is front-loaded with the core action and scope; the second provides valuable context about automation rules without redundancy. Every word earns its place.

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 simple list tool with one optional parameter and no output schema, the description sufficiently explains what the tool does and what the resource represents. It could mention return values or response format, but given the low complexity, the description is reasonably complete. The absence of output schema raises the bar slightly, but the tool's simplicity mitigates the gap.

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% for the only parameter ('enabled'), which already includes 'Filter by enabled/disabled status'. The description adds no additional semantics beyond what the schema provides, so the baseline of 3 applies.

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: 'List all automation rules for the team.' This clearly distinguishes it from sibling tools like get_automation_rule (which fetches a single rule) and create_automation_rule. It also adds context about what automation rules do, reinforcing the purpose.

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 the team' establishes scope, and the description implies this is the appropriate tool for enumerating automation rules. It does not explicitly mention alternatives or exclusions, but for a simple list operation, the context is clear enough to guide usage. The filter parameter for enabled status is also hinted by the description's 'List all', implying optional filtering.

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