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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the core safety profile is covered. The description adds that the sync is 'full' and pulls from specified platforms, but it does not disclose side effects, rate limits, whether it overwrites existing data, or what happens on failure. This is moderate added value beyond annotations.

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 with no redundancy. The first sentence front-loads the action and scope; the second adds a crisp usage condition. 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 zero-parameter trigger tool with no output schema, the description provides the essential purpose and usage context. It does not mention what the trigger returns or how to verify completion, but sibling tools like get_pipeline_status likely fill that gap, so this is a minor omission.

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?

The tool has zero parameters and the schema covers everything, so the baseline is 4. The description's mention of 'full product sync' and the source platforms implicitly scopes the operation, but no parameter-level elaboration is needed.

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 verb ('Trigger'), resource ('a full product sync'), and destination ('into Pollen'), and names source platforms. It clearly distinguishes this from enrichment and write-back siblings by adding 'Use before enrichment if products are missing or out of date.'

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 gives explicit context for when to use the tool ('before enrichment if products are missing or out of date'), which is strong guidance. However, it does not name alternative tools or provide any 'when not to use' exclusions, so it stops short of a fully explicit routing instruction.

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