get_spacetrack_gp

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

No annotations are provided, and the description only mentions basic requirements (env vars, at least one filter). It does not disclose read-only nature, rate limits, pagination, or side effects.

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 clear and structured with parameter list, but somewhat verbose. It could be more concise but is well-organized.

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?

Without output schema, the description fails to explain what the tool returns (e.g., fields of GP records). It also doesn't specify if it returns one or many records, leaving the agent underinformed.

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 description coverage, the description adds meaningful details for each parameter, including examples and format (e.g., epoch_range 'start--end'). It compensates well for the schema's lack of descriptions.

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 'Query GP (General Perturbations) records from SpaceTrack', using a specific verb and resource. It distinguishes from siblings like get_spacetrack_cdm and get_spacetrack_decay by specifying GP records.

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 notes that at least one filter parameter must be provided and requires environment variables, but does not guide when to use this tool over alternatives like query_spacetrack or get_spacetrack_gp_history.

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