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

With no annotations, the description carries the burden and does well: it discloses the return fields, that only one page is fetched, and the pagination contract (continue with nextOffset only when hasMore is true). It omits auth/rate-limit behavior, but the read-only nature and paging semantics are clearly conveyed.

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?

Four dense sentences, front-loaded with the core purpose, then return shape, then routing, then pagination. No filler or repetition.

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?

No output schema exists, and the description compensates by naming the returned fields (queryId, queryText, popularity, searchVolume, videoCount, trend). Combined with routing and pagination guidance, an agent has everything needed to call and chain it correctly.

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, limit, offset and language. The description adds only indirect value by explaining the pagination concept (nextOffset/hasMore), though it uses 'nextOffset' which does not match the schema's 'offset' param name.

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 (search) and resource (CSI topic records) with explicit scope exclusions ('not videos or accounts'). The agent can distinguish this from search_videos and search_users without opening any 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?

Explicitly names the alternative for finding videos (search_videos) and enumerates six downstream tools that consume queryId. It gives both when-to-use and when-not-to-use guidance with concrete routing.

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