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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds the returned field set and the underlying POST /items/get endpoint, but says nothing about result size, rate limits, or pagination behavior beyond what the schema already documents.

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?

Three compact fragments with the resource and return fields front-loaded, followed by filters and endpoint. Dense and waste-free, though the telegraphic phrasing slightly reduces readability.

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 no output schema, the description partially compensates by listing the fields returned (item number, prices, stock, UPC, categories, images). For a 9-parameter read tool whose schema is well documented, the only real gap is explicit pagination guidance in prose.

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 89%, so the schema already carries most parameter meaning and the baseline is 3. The description reinforces 'name (contains)' and names four filter shortcuts, but omits offset, page_size, sort_field/sort_direction and the generic filters array, which the schema documents anyway.

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 the product catalog') and enumerates the returned fields, so the agent knows this is the list/search counterpart to markettime_get_item. It does not explicitly name the sibling it replaces, keeping it just 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 filter list implies when this tool is appropriate (bulk catalog lookup by name/number/manufacturer/modified date), but there is no explicit when-to-use or when-not-to-use guidance versus markettime_get_item or markettime_list_item_pricing. Usage is inferable rather than stated.

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