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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety and idempotency are covered structurally. The description adds one useful behavioral qualifier — only *public* topics are returned — but says nothing about pagination behavior, ordering, or whether the list is stable/cached.

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, with the core capability front-loaded ahead of the follow-up usage hint. Every clause earns its place.

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-value documentation is not required, and annotations cover the safety profile. Combined with the description's mention of returned fields, this is nearly complete; the only meaningful gap is the absence of any pagination or result-size guidance.

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 0% for limit and offset, so the description is the only place meaning could be added — and it adds none. The parameters are conventional pagination with defaults and bounds in the schema, so an agent can infer intent, but the description fails to compensate for the coverage gap.

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 public topic names, slugs and record counts'), and even names the exact fields returned, so the agent knows the shape of the payload. It differentiates from siblings only indirectly, by pointing out that the emitted slugs feed 'search or list_days' rather than stating what this tool is not.

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?

The second sentence gives genuine downstream guidance on what to do with a slug ('use as the topic filter in search or list_days'), which implies this tool is the topic-discovery step before those calls. However, it never states when to call list_topics itself versus going straight to search/list_days, so usage is implied rather than explicit.

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