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

With no annotations, the description carries the full burden, and it does disclose some non-obvious traits: Zero-PII, lure-free content, and a fixed 24-hour window. However, it omits whether the call is read-only, whether it is rate-limited or costly, what the response looks like, and what 'AO-058' compliance implies for the caller.

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?

It is a single sentence with no filler, but it is dense with undefined internal jargon ('AO-058', 'Shadow-Compute', 'lure-free') that front-loads terminology rather than a plain statement of what is returned. Brevity is achieved at the cost of comprehension.

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?

For a zero-annotation, zero-output-schema tool, the description should compensate by explaining the payload and the section selector. Instead it leaves the return shape, the meaning of 'phylogenetics', and the identity of Protocol AO-058 unexplained, so an agent cannot confidently predict results.

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 coverage is 100% for the single 'section' parameter, so the enum and its descriptions are already documented. The description loosely echoes two of the three enum values (GDP breakdown, telemetry) but never explains 'phylogenetics', leaving the one non-obvious enum option unilluminated.

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 verb 'Returns' plus a list of payload items gives a rough sense of the resource, but the resource itself is defined only in opaque terms ('Shadow-Compute GDP sector breakdown', 'Protocol AO-058 domain telemetry'). An agent cannot tell from this what data it would actually receive or how it differs from the many sibling 'query_*' observatories beyond the topic label.

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?

There is no indication of when to select this tool over the numerous sibling query tools, no prerequisites, no exclusions. The only implicit signal is the 24h window, which is not framed as a usage condition. An agent must guess based on topic keywords alone.

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