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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds nothing beyond that — no mention of ordering, pagination, whether disabled rules are included, or what happens if the collection has no rules.

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 sentence with no filler, but it is under-specified rather than concise; the single clause carries almost no information beyond the tool name.

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 one-parameter read tool with no output schema and annotation coverage, the description should at minimum clarify the collection scoping and what a returned rule contains. As written, an agent knows the resource but not the scope or result shape.

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%, so the single required parameter collection_id is documented nowhere. The phrase 'on a list' loosely gestures at the scoping parameter but uses different terminology and never states that collection_id is required or what form it takes.

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 verb 'Lists' and resource 'automatic research rules' are named, so the basic operation is identifiable. However, 'on a list' is vague and inconsistent with the rest of the API's 'collection' vocabulary, and nothing distinguishes this from siblings like get_research_rule or get_research_rule_results.

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 use this listing versus get_research_rule (single rule), prepare_research_rule, or approve_research_rule. The agent must infer that this is the enumeration endpoint purely from the name.

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