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

Annotations already cover read-only, idempotent, non-destructive behavior, so the description adds useful context: it rechecks sources and offers, preserves user preferences, and requires user confirmation for changed items. It does not describe authentication or response shape, but an output schema exists.

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?

The description is two sentences with the primary action front-loaded and no obvious filler. The second sentence adds behavioral context, though 'Keep the user's preferences' is slightly vague.

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?

Given the full parameter schema, existing output schema, and read-only annotations, the description provides enough context for an agent to understand the tool's role and interaction requirement. It could be slightly more explicit about what 'sources and offers' means, but that is likely covered by the output schema.

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?

There is one parameter with 100% schema description coverage, including that it is the exact account-owned workflow_id. The description does not elaborate on the parameter beyond what the schema already provides, so the baseline 3 is appropriate.

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 clearly states a specific action on a specific resource: reopening the account's saved search and rechecking its sources and offers. It distinguishes itself from sibling saved-search tools like list_saved_searches and save_search, though it does not explicitly name those alternatives.

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 implied by 'Reopen this account's saved search,' indicating it is for continuing work on an existing saved search. However, it gives no explicit when-not-to-use guidance or comparison with siblings such as continue_search or start_search.

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