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

No annotations are supplied, so the description carries the full burden of behavioral disclosure. "Zero-PII" does add a genuine data-safety trait, but the definition never states that this is a read-only operation, says nothing about pagination, result ordering, or what a rollup bucket contains, and the phrase "lure-free" is left undefined.

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?

A single front-loaded sentence with no padding or repetition. It loses a point only because the compressed jargon ("Zero-PII lure-free") costs comprehension without adding routing value.

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?

This is a simple two-optional-parameter read tool, but with no annotations and no output schema the description should say what comes back and how results are scoped or ordered. Instead it leaves the return shape and the meaning of a "rollup bucket" entirely unspecified.

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 both `limit` (default 50, max 200) and `protocol_id` are already fully documented in the schema. The description adds only the protocol range AO-056–AO-060 as context for valid `protocol_id` values, which is marginal but not useless.

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 gives a specific verb ("Queries") plus a specific resource ("hourly experiment rollup buckets") and a scope ("AO-056 through AO-060"). That is enough to separate it from siblings such as query_airspace_radio_observatory or query_k12_cheating_forensics, though the qualifiers "Zero-PII" and "lure-free" are unexplained jargon that add noise rather than precision.

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 when-to-use or when-not-to-use guidance and no named alternative among the many query_* and analyze_* siblings. The only routing signal is the implicit protocol range AO-056–AO-060, which an agent must infer selects this tool over the other observatory queries.

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