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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely non-obvious context: no paging (one call returns everything), counts are computed live per call, one call consumes a unit of the key's quota, and a rejected argument costs nothing. It stops short of describing result shape or failure modes, but the annotation bar is met.

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-loads purpose, then routes to siblings, then groups parameters and behavior into labelled clauses so the reader can stop early. Dense but nearly every sentence carries a distinct fact; only the restatement of default-domain/locale omission overlaps the schema.

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?

An output schema exists, so return values need not be explained, and the description still covers filtering semantics, ordering, lack of paging, live counts and quota cost. Nothing an agent needs in order to call it correctly is missing.

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 baseline is 3, but the description adds semantics the schema does not: a topic can belong to several domains so `domain` filters rather than isolates, and `locale` translates names and descriptions. The omission behavior is restated from the schema, which is redundant but harmless.

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 ('List AiSeek's published topics') and defines what a topic actually is (curated subjects grouping related changes), plus what comes back (90/7-day counts and newest change). It is immediately distinguishable from get_topic and search_changes.

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 says to use it 'to browse by subject or category and to find a slug for get_topic', and names the alternative for a different intent ('for free-text search use search_changes'). Both the when and the when-not are stated.

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