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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the bar is lower, and the description still adds real context: it discloses the access-token prerequisite ('Works only when this connector carries the account's access token') and warns that brands, names, variants, notes and folder names are raw account-typed text returned unchanged — a useful trust/prompt-injection signal. It also states the default ordering, which annotations do not cover.

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?

Front-loaded with the resource and ordering, which is good, but a large share of the text is a field-by-field inventory of the response ('brand, name, variant, gear type, grams..., product link and folder') that duplicates the output schema and does not help an agent decide or invoke. The remainder is 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 four-parameter read with an output schema, the description covers the essential unknown — the auth-token precondition — plus default ordering and text passthrough. Pagination mechanics live in the schema, and return shape is covered by the output schema, so nothing critical is missing; only the sibling routing is under-specified.

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 all four parameters are already documented, including limits, the Chinese-character query nuance, and the empty-string folder case. The description adds only the default sort order ('most recently used first') and a paraphrase of query ranking, so it neither compensates for nor extends the schema meaningfully — baseline 3.

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+resource: reads the gear the connector's account owns, returns it most-recently-used first, and enumerates what each entry contains. It is clear what the tool returns, but it never names or contrasts itself with siblings like search_catalog or get_list, so an agent must infer the boundary on its own.

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?

'A query ranks by a search instead; a folder name keeps to that folder' explains how parameters steer results, which implies when to use them, but there is no explicit when-to-use/when-not guidance and no named alternative for catalog-wide search or for mutating gear (edit_my_gear). 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.