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

Annotations only declare readOnlyHint=false and destructiveHint=false, which provide limited safety context. The description adds valuable behavioral insight: picking an existing catalog will cause Pollen to manage (add/remove) products in it, and creating with '__create__' will generate a dedicated catalog. This goes beyond the annotations and informs the agent of side effects.

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?

Two sentences, no filler. The core action and status are front-loaded, and the critical safety constraint is delivered in the second sentence. Every word earns its place.

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 single-param tool with full schema coverage and no output schema, this description covers when to use, how to use, parameter semantics, and a key safety rule. Nothing an agent needs to invoke it correctly is missing.

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 coverage is 100% with a clear description for catalogId. The tool description adds deeper semantics: it explains that '__create__' triggers creation of a catalog named 'Pollen - {shop}', and that the id must come from the candidates list. This enriches the parameter meaning beyond the schema's basic description.

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 uses a specific verb ('Resume') with a precise resource ('Meta connect paused on the catalog picker') and names the action (pass a catalog id or '__create__'). It clearly distinguishes this tool from the sibling 'pick_meta_business' by focusing on the catalog step in the Meta connection flow.

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?

It explicitly states when to use: when the connection is in 'selecting_catalog' status. It also provides a strong exclusionary guideline ('NEVER pick an existing catalog without the merchant's explicit confirmation'), which is critical for safe usage. It doesn't name explicit alternatives, but the context and caution make usage clear.

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