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

Annotations already declare readOnlyHint/idempotentHint/destructiveHint=false, so the safety bar is low, and the description adds substantial interpretation guidance instead: GB notes carry an assimilated-law caveat, editorial status can be draft or published, and 'anything not method=human is evidence, not a finding.' That last warning materially changes how an agent should treat the data. It does not touch auth, rate limits, or sizing, so not 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?

A single front-loaded sentence ('Everything a topic page shows: ...') with no filler, and every clause maps to a distinct part of the payload. It is dense with em-dash-nested qualifiers, which slightly hurts scannability, keeping it from a 5.

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 present, return values need not be explained, and annotations carry the safety profile; the description usefully adds the interpretive caveats. The missing piece is routing guidance against the many sibling retrieval tools, which leaves a small but real gap for a single-topic fetch.

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%: conceptId is documented with a concrete example ('local:topic-pre-contract-information'). The description adds no parameter-level detail beyond the schema, so the baseline of 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+resource ('get_topic') and then enumerates exactly what a topic page contains: orientation paragraph, per-jurisdiction notes, anchored provisions, transposition links, related instruments. This is far beyond a tautology. It stops short of naming sibling tools (list_topics, provisions_by_concept) by name, so the differentiation is implied rather than explicit.

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 description never says when to use get_topic versus alternatives such as list_topics (list vs single), provisions_by_concept, or lookup_provision/provision_context. There is no when-to-use or when-not guidance, only an inventory of returned content, so the agent must infer the routing itself.

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