plot_orbit_elements_from_gp

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

No annotations provided, so description should disclose behavioral traits. It mentions 'plot' but doesn't specify whether it saves a file, displays, or returns the plot. Missing side-effect information.

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?

First sentence is clear, but the Args block adds verbosity. Could be more concise, e.g., integrating parameter explanations into a single paragraph.

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 no output schema, description should explain plot output (e.g., axes, title). Also missing information on return value. Tool complexity and multiple siblings demand more completeness.

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?

With 0% schema coverage, description adds meaning by explaining 'gp_record' as from celestrak/spacetrack, epochs as ISO strings, and defaults for propagator_type and step_seconds. Could still clarify which orbital elements are plotted.

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?

Description clearly states it plots Keplerian orbital element evolution from a GP record. However, it fails to differentiate from sibling 'plot_orbital_elements' which may have similar functionality.

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?

No explicit guidance on when to use this tool versus alternatives like 'plot_orbit_elements' or 'plot_gp_history_elements'. The context of usage is not addressed.

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