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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered. The description adds no behavioral context beyond that — nothing about pagination behavior, result ordering, or what a 'rule' record contains in practice — so it contributes essentially nothing on this dimension.

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?

It is very short and front-loaded, but the brevity comes from under-specification rather than disciplined editing — a bare noun phrase with a parenthetical. No sentence is wasteful, yet the single fragment cannot carry the tool's semantics.

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 tool with no output schema, the description should at minimum convey that it returns a paginated collection of Meta auto-rules and how that differs from the sibling list_auto_rules. Neither is present, and the parenthetical about conditions/actions/schedule hints at record structure without confirming it.

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?

All three parameters (page, search, per_page) have complete schema descriptions with defaults and bounds, so the schema carries the burden. The description does not mention filtering or pagination at all, adding no meaning beyond the structured fields; baseline 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 fragment 'Facebook auto-rules (conditions, actions, schedule)' identifies the resource and its constituent parts, so an agent knows it concerns Meta/Facebook auto-rules. However, it supplies no verb (the 'list' action is only inferable from the name/title) and does not distinguish it from close siblings such as list_auto_rules, get_auto_rule, create_auto_rule, or list_auto_rule_runs. Purpose is guessable but not stated.

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 when-to-use guidance, no mention of prerequisites (e.g. a linked Meta account or cabinet), and no routing to alternatives. With list_auto_rules present as a sibling, the absence of any disambiguation is a real gap rather than a minor omission.

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