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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful scope context ("across shops") but does not disclose pagination behavior, rate limits, authentication needs, or result format beyond what annotations already imply.

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?

The description is a single front-loaded sentence with no filler. It immediately states the operation, resource, scope, and input type.

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?

Given the simple search complexity, complete schema descriptions, existing output schema, and annotations, the description is nearly sufficient for correct invocation. The only meaningful gap is the absence of usage routing among sibling search and detail tools.

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 q, limit, and offset are already documented in the schema. The description maps "keyword query" to the q parameter but adds no extra syntax, default, or pagination guidance beyond the schema.

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 gives a specific verb ("Search"), resource ("Etsy product listings"), and scope ("across shops"), and it clarifies the input is a keyword query. This distinguishes it from siblings such as etsy_shop_search (shop search) and etsy_listing (single-listing detail) without requiring the schema.

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 states what the tool does but gives no explicit when-to-use guidance, no when-not-to-use conditions, and no alternatives such as etsy_shop_search or etsy_listing. An agent must infer that this is the general keyword search tool from the name alone.

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