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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so safety is covered. The description adds value beyond that by disclosing result ordering ('newest first'), the paged nature of results, that counts accompany topics, and the intended one-shot orientation behavior — details the annotations cannot convey.

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 output shape front-loaded and the calling condition second. Every clause carries information an agent would otherwise have to guess.

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 rich annotations, a full-coverage schema, and an output schema handling return values, the description covers what is needed to call it correctly. Minor residual gap: it never mentions how the returned next_cursor feeds back into the cursor parameter for paging, though the schema implies it.

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%, so all four parameters (limit, topic, cursor, language) are already documented. The description only reinforces that 'topic' is optional and narrows results, adding no syntax or format detail beyond the schema, which puts it at the baseline 3.

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?

The description names the concrete outputs — 'Topics in use (with counts)' plus 'a page of published knowledge records, newest first' — which is a specific, distinctive shape an agent can tell apart from a keyword search or single-record fetch. It does not name any sibling tool, so differentiation is inferred rather than stated.

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?

'Call it once when you do not know whether this network covers a subject' gives a clear triggering condition and even bounds the invocation frequency (once), which is unusually actionable. It does not state when to prefer search_knowledge or get_knowledge instead, nor any exclusion.

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