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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered. The description adds valuable non-annotation context: works without a key for Shopify/WooCommerce, one request per page up to 250 products, and requires a free SnoopScan key. It does not contradict 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?

Front-loaded with the core purpose, then capabilities, then the key requirement. Structured in short paragraphs. The odd line break before 'Needs a free SnoopScan key' is minor but does not hurt readability much.

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?

An output schema exists, so return-value details need not be repeated, and the description confirms the return fields without over-explaining. It covers platform support, pagination, and auth requirement. It could more explicitly state the required url parameter's intent and limit's default, but it is substantially complete.

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 0%, so the schema provides no parameter descriptions. The description compensates by explaining pagination ('one request per page of up to 250 products'), which gives meaning to the limit parameter, and implies the url targets a store catalog. It stops short of documenting the limit default or format specifics, so not a 5.

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 every product a store publishes, from the store's own catalog'), and scopes it to a store's catalog, distinguishing it from generic listing siblings like listPosts and listMonitors. An agent can tell this is product enumeration, not scraping or monitoring.

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?

Implies usage by stating it works for Shopify and WooCommerce without a key and noting pagination, but never says when to use this over siblings like scrape, extract, or map. No explicit exclusions or conditions are given.

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