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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so the safety profile is covered. The description adds useful context beyond annotations: the data is free, attribution is required to CelesTrak, and a fallback source is specified. It does not mention rate limits or response format details.

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 description is front-loaded with the primary when-to-use guidance and the key data fields. The license and attribution details are necessary but make the sentence dense. There is little wasted text, though the ending 'Via cev-os TRIPWIRE' is slightly opaque without context.

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-parameter tool with no output schema, the description provides enough to understand what data is returned and how it is meant to be used. It lists representative orbital fields and explains SGP4 propagation, though it does not specify response format or units.

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 tool has zero parameters, so there are no parameter semantics to clarify. Per the rubric, zero parameters establishes a baseline of 4. The description's mention of orbital element fields is output-related rather than parameter-related.

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 specific resource: the International Space Station's current orbital elements from CelesTrak OMM, including epoch, inclination, mean motion, eccentricity, altitude, and orbital period. It explains the intended use for SGP4 propagation. It does not explicitly differentiate from siblings, but none of the siblings are similarly scoped.

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?

It gives a clear usage condition: use this when you need ISS orbital elements to propagate position yourself with SGP4. It also identifies the fallback data source, wheretheiss.at, but does not state when not to use the tool or name alternative tools.

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