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

Annotations already declare destructiveHint=true and openWorldHint=true, and the description usefully adds that a pause preserves running searches and that resume does not raise limits. However, for a tool whose enum includes 'deleted', it says nothing about whether deletion is permanent, what happens to queued searches or historical results on delete, or what a version conflict returns.

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?

Three short sentences, front-loaded with the operation and followed by the two non-obvious behavioral constraints. 'A resume never raises the limits' is terse but genuinely informative; no sentence is padding, though the delete case is conspicuously absent from an otherwise well-structured note.

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 destructive three-parameter mutation with no output schema and no parameter documentation, the description covers state transitions but omits the destructive-path consequences and the versioning contract. An agent could call it correctly for pause/resume but would be guessing on delete and on conflict handling.

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 description must carry the burden. It explains the active/paused semantics but never mentions rule_id or expected_version; the latter is the optimistic-concurrency token and an agent gets no hint about why version 1+ must be supplied or how a mismatch is handled.

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 list ('Pauses, resumes or deletes') and names the resource ('a rule'), so the operation is unambiguous. It does not differentiate from nearby siblings such as approve_research_rule or prepare_research_rule, leaving the agent to infer which rule-lifecycle tool applies.

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?

Usage is only implied through the state-transition semantics: pause holds queued searches, resume returns to active. There is no explicit 'use this when' or 'do not use this instead of approve_research_rule' guidance, and the conditions under which deleting is preferable to pausing are unstated.

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