List guardrails and automations

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered; the description adds only the HTTP endpoint, which is not behaviorally useful to an agent. Nothing is said about pagination, result ordering, default filtering, or whether disabled rules are included — the details that actually shape a list call.

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?

One short, front-loaded sentence with no filler; the resource is stated before the endpoint detail. It is terse to the point of under-specification rather than verbose, so nothing needs trimming.

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 list endpoint with no output schema and no parameter documentation in the schema, the description should describe what comes back (fields, shape, pagination) and how the two filters combine. Neither is present, leaving the agent to discover result structure empirically.

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 0%, but both parameters are enums (kind: guardrail|automation, enabled: true|false) whose accepted values are self-describing, and both are optional so the no-arg case defaults to listing everything. The description adds no filtering semantics, though the marginal value lost is small given the enumerated values.

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 states a specific verb and resource ("List guardrails and automations") and echoes the underlying endpoint (GET /v1/rules), so the agent knows this is a read that returns both rule kinds. It stops short of distinguishing the result from siblings like rules_get or rules_runs, but the verb/resource pairing is unambiguous.

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 call this versus rules_get, rules_runs, or rules_simulate, and no mention of prerequisites or typical follow-up. The agent must infer usage purely from the tool name and the sibling set.

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