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

Annotations already cover the safety profile (readOnly, idempotent, openWorld), and the description adds real value by disclosing the licensing state and that data comes from a local cache, never fetched from CelesTrak per caller. However, it omits the operationally critical consequence of that caching — how stale the cached element sets may be or how often they refresh — which is exactly what an agent propagating orbits needs to know.

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?

Front-loaded with the use condition and resource, then the licensing constraints in a compact tail. The attribution sentence is slightly repetitive (the CelesTrak name and URL appear twice across the license and attribution clauses), but no sentence is filler.

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 no output schema, the description does name the payload format (OMM element sets) and where it originates, which is the essential return-value context. The remaining gap is cache freshness and whether 'limit' truncates deterministically, both of which matter for a two-parameter propagation-feed tool.

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%, with the group enum and the 1-500 limit range already documented in the schema. The description restates the group list but adds nothing about the limit parameter (pagination, ordering, or what happens when the group exceeds the cap), 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?

States a specific verb and resource: retrieve CelesTrak GP orbital elements (OMM) for a TRIPWIRE-cached group, explicitly listing the five supported groups and the downstream purpose (self-propagation with SGP4). It stops short of naming the closest sibling, get_iss_orbit, so the boundary between 'cached group catalog' and 'live ISS orbit' is left implicit.

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?

The opening clause is a genuine when-to-use condition ('when you need ... to propagate yourself with SGP4'), which tells the agent this is for local propagation rather than ready-made position data. It does not state when to prefer an alternative such as get_iss_orbit for a single-object position.

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