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

The annotations already flag destructiveHint=true and idempotentHint=true, and the description earns credit by explaining what the destruction means concretely: rows the source dropped are removed. It doesn't disclose permissions requirements or what the call returns (e.g., counts of added/removed rows), which would complete the picture for a destructive write.

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 short, front-loaded sentences with zero filler; the destructive side effect is stated parenthetically right after the action, and the sibling pointer comes last.

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?

There is no output schema, and the description says nothing about what a successful sync returns or how failures (e.g., the app not connected) manifest. For a destructive, open-world operation this is an adequate but not complete definition.

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 both id and slug documented in the schema itself. The description adds no parameter-level meaning beyond that, so the baseline of 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?

States a specific verb and resource: re-read the source of an app-fed collection, plus the side effect of dropping removed rows. It differentiates from refresh_products by scoping that tool to Stripe products, though it doesn't distinguish itself from collection siblings like import_collection_csv or list_collection_rows.

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?

The 'Stripe products: refresh_products' line gives an explicit alternative for one case, which is real routing guidance. It lacks explicit when-to-use criteria for the core case (e.g., when to sync versus re-importing via import_collection_csv), so it stops short of full coverage.

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