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

Annotations declare readOnlyHint=false and openWorldHint=true, which is unusual for a 'search' tool. The description's mention of a 'locally synced Etsy category library' and the syncEtsyCategory trigger hint at why, but it never explicitly discloses the side effect or whether a call can mutate/sync state. It adds data-source context beyond annotations but leaves the main behavioral question unanswered.

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?

Purpose is front-loaded in the first sentence, but the second is an over-stuffed trigger list with redundant phrasing ('even if the tool name is not mentioned, as long as...'). It is usable but not tight.

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 simple 3-parameter lookup with no output schema, the description covers what is searched, the data source, and the purpose. The only real gap is explaining the readOnlyHint=false side effect, which keeps it from a 5.

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 keyword substring matching, page, and pageSize. The description's 'by name, ID, or parent IDs' mirrors the keyword schema description without adding syntax or constraint details, so 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 and resource ('Search Etsy category data') and adds scope ('by name, ID, or parent IDs' for 'product/store filtering'). Clear enough to distinguish from product-search siblings, though it never names the near-identical nexscope_data_eh_etsy_etsy_category_search sibling.

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 trigger sentence gives explicit when-to-use conditions (user mentions Etsy category, category ID, category tree, syncEtsyCategory) and a goal condition ('find a category ID by keyword'). It lacks any when-not guidance or named alternative, which keeps it below a 5.

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