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

Annotations only declare readOnlyHint=true; the description adds that it takes no arguments and 'reads nothing,' clarifying this is a static catalog with no server-side lookup or side effects, and that a single call suffices. It does not describe the return shape, but that is the only notable omission.

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 clauses: what you get first, then the usage instruction. No filler words, no restatement of the tool name, and every clause carries information.

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 and no parameters, the description must convey the payload, and it does by naming the three content categories returned. It is adequate for a zero-argument discovery tool, though it could say a bit more about the form of the returned catalog.

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?

There are zero parameters, so the baseline is 4. The description correctly states 'takes no arguments,' matching the empty schema rather than contradicting it.

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 specific resources returned — section templates, node types, and breakpoints — which is far more concrete than the tool name alone. It does not, however, name any sibling (e.g. list_collections, list_items) to disambiguate which listing tool an agent should pick.

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 are about to build' gives an explicit trigger condition and cadence, which is strong guidance. It stops short of naming alternatives or stating when NOT to call it, keeping it below a 5.

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