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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so credit here goes to what the description adds: that the institutional read is 'longer and assumes more', and that omitting as_of silently returns the newest edition. Both are real behavioral facts not derivable from structured fields.

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?

Very compact — one paragraph with the core capability front-loaded before parameter details. The em-dash clause and parenthetical defaults are dense but every clause carries information; nothing is padding.

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?

An output schema exists, so return values need no explanation, and all three parameters get semantic treatment. The one gap is how an agent discovers valid 'area' values — no pointer to list_coverage — which is minor but real for a required parameter.

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 0%, so the description carries the full burden and largely meets it: it enumerates scope values with the default, gives the as_of date format and its fallback behavior, and provides example area slugs. The area parameter's accepted vocabulary is still only shown by example, not defined.

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 resource — one coverage area's note, in full — and anchors it with concrete area slugs ('real-assets-shipping', 'real-assets-aviation'). The 'one ... in full' framing contrasts implicitly with the sibling list_coverage, though no sibling is named explicitly, which keeps it 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?

It explains how to use the scope and as_of parameters (defaults, what 'institutional' implies, newest vs past edition), which is useful operational guidance. It never says when to reach for this tool rather than list_coverage or the executive-note siblings, so usage routing is only implied.

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