gold_etsy_find_category

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

With no annotations, the description carries the full burden, and it uses that space to flag BYOK and paid-only access, and to state the output is a category_id for create_listing. That is meaningful behavioral info. It still omits match multiplicity/error behavior, but for a simple lookup the core side effects and prerequisites are disclosed.

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 core behavior is front-loaded in the first sentence and the caveats are kept short. The phrase 'No more guessing numbers' is filler, but not costly.

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?

The description provides the essential integration (category_id into create_listing) and access constraints, which is enough to start using it. Without an output schema, it should clarify whether multiple category matches are returned and how limit behaves; the cryptic 'BYOK' and 'PAID ONLY PRO $29' also benefit from more precision.

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?

The query parameter is explained by the 'by keyword' phrasing and schema examples, and limit, while undocumented, is an optional number with a sensible default and name. At only 50% schema coverage the description does not directly explain limit, so it is not exemplary, but it doesn't need to overcome a large gap.

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 concrete action ('Search Etsy's full seller taxonomy'), specifies input ('keyword') and exact output ('category_id'), and ties it to create_listing. This clearly separates it from sibling listing/inventory tools.

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?

Tells the agent this is the category-ID lookup companion for create_listing ('you can paste into create_listing'), so its use context is explicit. It doesn't spell out when not to use it, but no sibling tool covers this same category-lookup function.

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