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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. The description contributes the non-obvious behaviors: results are paginated, ordered by last modification, and the "search" parameter narrows the index rather than re-ranking it. No rate limits or result-shape notes, but the output schema covers returns.

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?

Two sentences, zero filler. The scope-and-ordering statement comes first, then the filtering hint, then the sibling routing — a sensible front-loaded order for an agent scanning for a routing decision.

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 an output schema handling return values, full annotation coverage of the safety profile, and a fully described four-parameter schema, the description fills precisely the remaining gaps: catalogue scope, ordering, filtering semantics, and sibling disambiguation. Nothing needed to select or call it 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 the baseline is 3, and the description earns above that by clarifying that "search" acts as a narrowing filter over this catalogue rather than triggering relevance matching — a semantic distinction the schema's terse "Optional keyword filter" does not convey. Pagination and the type enum are left entirely to the schema.

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?

Names a specific operation (paginated index), the exact resource set (posts, pages, listings, market insights), and the sort order (newest-modified first). It also explicitly distinguishes itself from the two relevance-search siblings, so an agent can route correctly 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?

States the positive case ("enumerate or audit the full catalogue") and names the alternatives for the contrasting case ("For relevance-ranked matching of a single topic use sem.search_content or sem.find_related"). Both the when and the when-not are explicit.

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