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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds genuinely new behavior: filter conjunction semantics, the default exclusion of drafts/archived/unlisted/unpublished products, and the worst-first ordering. Pagination is mentioned but page size behavior is left to the schema.

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?

Front-loads purpose, then behavior, then ordering — a sensible order with little waste. The parenthetical list of excluded item types is slightly verbose but is the operative detail for the includeUnpublished flag.

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 read-only list tool with nine fully documented parameters and an output schema, the description covers everything an agent needs to call it correctly: default exclusion behavior, filter combination, and sort order. Return shape is delegated appropriately to 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?

Schema coverage is 100%, so the schema already documents all nine parameters including defaults, ranges, and the 'false is ignored, not inverted' nuance. The description's one addition beyond the schema is the statement that filters combine (AND semantics), which is useful but is the same fact already implied by the includeUnpublished sentence, so it stays at baseline.

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 ('List the store's synced content'), enumerates the resource kinds (products, collections, pages, blogs, articles) and the returned fields (SEO fields, meta score 0-100). It does not name or contrast with siblings such as list_seo_issues or get_resource, so an agent must infer the boundary itself.

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?

Provides real usage context: filters combine, unpublished items are excluded by default with the rationale that SEO work on them is wasted, and results come back worst-score-first. It never says when to pick this instead of list_seo_issues or get_resource, so the when-to-use guidance is implied rather than explicit.

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