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

Annotations already declare read-only, idempotent, non-destructive and closed-world, so the safety bar is low; the description adds genuinely new behavior — that a ready citation is always included, that 'cost-shape' is never a price, and the important epistemic caveat that it describes general element behavior, not a specific building's condition, and that its limitations must be carried through.

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?

The core purpose is front-loaded, but the rest is one immense run-on sentence cramming a dozen content domains, format semantics and a disclaimer together, with the caveat buried at the end where it is easy to skim past.

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 a full output schema and complete parameter descriptions, the description only needs to cover scope and caveats, which it does: content coverage, citation inclusion, jurisdiction coverage and the general-vs-building-specific limitation. It is complete, just badly packaged.

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 the baseline is 3; the description restates the two formats and enumerates section ids that the schema already lists, adding only the qualifier that cost-shape is a shape rather than a price.

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?

Opens with a specific verb and resource ('Retrieve one Technical Library page by slug, element name or canonical URL') and then enumerates the page's content domains, so an agent can distinguish it from list_technical_pages or the paper/method siblings without opening the schema.

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?

It explains the default/modified retrieval modes ('By default a summary...; section returns one section, format full the whole page'), which is useful usage guidance, but it never states when to prefer this over a sibling like list_technical_pages or search_research, nor any when-not conditions.

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