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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds useful context beyond annotations: 'no auth required' and the fact that responses can be large (e.g., 'starlink' with ~6000 sats, 'active' with ~7000) which informs agents about scale and potential latency.

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 first two sentences are concise and front-loaded, but the lengthy list of supported groups largely duplicates the schema's enum description Bonus detail like approximate satellite counts adds some value, but much is redundant. The inclusion of 'Data from US Space Force, no auth required' at the end is useful but slightly misplaced. Overall, the description could be trimmed to reduce redundancy.

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?

Given the tool's simplicity (one enum parameter) and the presence of an output schema, the description covers the essential operational aspects: return content, data source, and no-auth requirement. It does not mention pagination or limits for large groups, but that is a minor gap for a read-only tool with such a straightforward interface.

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?

The input schema covers 100% of the parameter semantics, with the 'group' property description already providing detailed explanations for many groups (including counts and examples). The tool description adds no new parameter-specific information beyond what the schema already provides, so the baseline score of 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 clearly states the verb ('Retrieve') and the specific resource ('TLE orbital element sets for an entire predefined satellite group from CelesTrak'). It also enumerates what the response contains (NORAD catalog number, international designator, epoch, and full orbital parameters), making the purpose unambiguous. The emphasis on 'group' distinguishes it from sibling tools like individual TLE lookups or searches.

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 description clearly implies its intended use case (fetching TLE data for entire predefined groups) but does not explicitly state when to use this tool versus alternatives like individual satellite lookups or searches. It provides no exclusions or alternative routing, leaving some inference to the agent.

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