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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the description doesn't need to restate that this is a write. It adds useful context—data goes back as metafields/meta_data and should occur after enrichment—but it does not disclose prerequisites like store connection or whether existing metafields are overwritten.

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 three short sentences, each adding distinct value: what the tool does, when to run it, and what user phrases should trigger it. It is front-loaded and free of filler.

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 zero-parameter tool with no output schema, the description covers the core invocation requirements: the action, the target format, the timing, and trigger phrases. It is slightly light on preconditions like connection/auth, but the sibling connect_* tools and annotations make that gap minor.

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 are no parameters in the input schema, so there are no parameter descriptions to supplement. The tool's behavior is fully represented by the action and target format described, making the schema coverage complete and the baseline of 4 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 states a specific action ('Push enriched data back') and a specific resource ('the merchant's platform as metafields/meta_data'). It clearly conveys that this is a write/publish operation, though it does not explicitly contrast with siblings like sync_catalog or update_product_facts.

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 description gives explicit usage context: 'Run after enrichment completes' and provides recognized trigger phrases ('publish' or 'push to my store'). It does not mention exclusions or alternatives, but the usage timing and trigger language are clear enough.

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