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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is fully covered without description text. The description adds genuine context beyond that: the product domain (spreadsheets through printed goods), that prices are in USD, and that both a product page URL and an Etsy listing URL are returned. It omits pagination/limit behavior and how filters combine, which keeps it from a 5.

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 the purpose and returned fields front-loaded, then filters. The parenthetical product list ('spreadsheets, printables, templates, planners and printed goods') partially duplicates the collection enum's own descriptions, which is mild waste but not damaging.

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?

With an output schema present, the description needn't enumerate return values, and all parameters are schema-documented. For a zero-required-parameter, read-only catalog listing, everything an agent needs to decide and invoke is present.

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 description coverage is 100%, so all five parameters including enum values, lengths and defaults are already documented in the schema. The description restates four of the five filters at a looser granularity and omits `limit` entirely, adding no semantics beyond the schema. Baseline 3 applies.

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 ('Lists') and resource ('ProfitDrawer products'), and enumerates the product domain plus the fields returned (name, USD price, formats, availability, URLs). It does not distinguish itself from the sibling search_profitdrawer, which an agent could plausibly pick instead, so it stops short of a 5.

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 implies browsing/filtering by naming 'Optional filters: words to match, collection, maximum price and file format', which hints at when the tool applies. But it never says when to prefer it over search_profitdrawer or list_categories, and gives no exclusions or prerequisites.

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