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

With no annotations, the description carries the full burden and does well: it discloses payload contents (operatorMix, FCC rows, disputes, ituRecorded), source vintage with a tleStale threshold of 45 days, that ITU filings are not in the product, that SNS Online shut down in Jan 2025, and that TLE longitude is a tracked position not an assignment. It omits confirmation of read-only behavior and response shape, but the data caveats are substantial.

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 purpose is front-loaded, which is good, but the body is a stream of disjoint caveats (operatorIdentity split, ITU source, SNS shutdown, TLE semantics) without structure. Every fact is arguably relevant but the density and lack of grouping reduce scanability.

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 single-parameter, no-output-schema get tool, the description supplies rich data semantics and provenance caveats that an agent needs to interpret results. It lacks a clear statement of what the tool returns structurally and how it relates to clarke_get_slot, but is otherwise complete for invocation.

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% — the single 'slug' parameter is fully documented with a pattern and example ('101w'). The description adds no additional meaning about the slug beyond the schema, so baseline 3 applies.

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 says it returns an 'Agent slot record for one GEO position' and shares the payload of clarke_get_slot, which conveys it's a retrieval tool. But it never explains what 'terminal' means or how this differs operationally from clarke_get_slot — saying 'same payload' suggests a near-duplicate without defining the distinction. Purpose is inferable but the resource identity is muddled by the naming mismatch.

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 explicit when-to-use guidance: it does not say when to call clarke_get_terminal versus clarke_get_slot or the list_* siblings. Mentioning 'same payload as clarke_get_slot' implies equivalence rather than selecting between them, and the operatorIdentity/ITU caveats are data notes, not usage rules.

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