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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description adds useful behavior beyond them: the accepted identifier provenance, the ranked ordering of brands, and the fact that dates and answer counts accompany the result. It does not cover failure modes for an unknown/invalid topic id, keeping it short of a 5.

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 trigger, then identifier sources, then return contents, then next tools — a sensible order. The return enumeration in the middle sentence is long and slightly list-like, but each clause carries information an agent would otherwise have to infer.

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 carries the return-value burden and does so explicitly (name, market, questions, brands in page-rank order, dates, answer counts). Input provenance and follow-up tools are also covered, so nothing essential is missing for a one-parameter read tool.

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% and the single parameter's schema text already explains the id/fetch-id/slug forms with examples. The description repeats 'takes a topic id from parse_search, or a question's slug' without adding syntax or format detail, so baseline 3 applies.

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 (get a topic) and enumerates the returned payload — name, market, constituent questions, mentioned brands, ranking order, dates, answer counts. That payload profile clearly separates it from sibling getters like parse_get_prompt or parse_get_brand.

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?

Opens with an explicit trigger phrase (user asks which brands AI recommends / wants the topic behind a question), specifies accepted ID sources (parse_search id or question slug), and routes onward with named alternatives (parse_check_brand, parse_search). Both when-to-use and next-step guidance are present.

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