propagate_sgp4

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

No annotations are provided, so the description must disclose behavior. It states the model and parameter usage but does not mention that the tool is read-only/non-destructive, what the return format is, or any error conditions. Propagation is inherently non-destructive, but the lack of explicit safety confirmation is a gap.

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 relatively concise, using a short paragraph followed by a bullet-like list for arguments. It front-loads the purpose. However, it could be more structured with separate sections for usage and arguments.

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 8 parameters, no output schema, and no annotations, the description covers parameter semantics well but lacks information about output format, error handling, and whether it modifies state. The model mention helps differentiate from siblings, but return value details are missing.

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 0%, so the description adds meaning beyond the schema. It explains each parameter, provides example ISO strings for epochs, lists output frame options, and notes defaults like step_seconds=60 and angle_format='degrees'.

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 tool propagates a satellite orbit using SGP4/SDP4 from TLE data, specifying the verb, resource, and model. It also differentiates from siblings like propagate_keplerian and propagate_numerical by naming the model.

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 explains the two usage modes (single epoch or range) and lists parameters with types. However, it does not explicitly state when to use this tool versus alternatives like propagate_from_gp_record or propagate_keplerian, though the model mention implicitly guides.

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