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

No annotations are provided, so the description carries the full behavioral burden. It discloses the shape of each returned record (code, names, shape, series count), but says nothing about result size, ordering, or whether the catalogue is exhaustive or filtered — the kind of context that matters for a discovery tool.

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 short sentences, front-loaded with what you get and followed by the next step — no waste. The terseness borders on cryptic ('shape'), costing a point.

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 no output schema, the description must explain return values, and it only gesture toward them — 'shape' is undefined jargon and there is no indication of how many topics come back or their structure. Adequate as a signpost, thin as documentation.

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?

The tool takes no parameters and the schema is an empty object, so there is nothing to disambiguate. Baseline of 4 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 the resource (the catalogue's topics) and its returned fields — code, names, shape, series counts — which is specific enough to tell it apart from get_series or search_series. Sibling differentiation is only implicit via 'then get_topic', so it stops short of a 5.

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?

'Start here, then get_topic' gives an explicit sequential entry point and names the concrete follow-up tool. It does not state any exclusion or when *not* to use it, but for a zero-parameter discovery tool the routing guidance is clear.

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