get_celestrak_sup_gp

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

No annotations provided. Description does not disclose any behavioral traits such as data freshness, rate limits, pagination, or error handling, leaving agents unaware of important operational characteristics.

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?

Extremely concise: one-line summary, one-line context, then Args section. No redundant information, front-loaded, easy to parse.

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?

Adequate for a simple lookup tool: explains purpose and parameters. However, lacks description of return format or error conditions; with no output schema, more detail would improve 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?

Description adds meaningful details beyond schema: source is case-insensitive with examples, limit is max records. With 0% schema coverage, this compensation is good, though not exhaustive (e.g., no default limit behavior).

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 'Look up supplemental GP records from CelesTrak by source' and differentiates from standard GP by explaining supplemental data are operator-provided ephemerides, which distinguishes it from sibling tool get_celestrak_gp.

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?

Description implies use for supplemental ephemerides and gives example sources, but does not explicitly state when to use versus other tools like get_celestrak_gp or query_celestrak, nor provides exclusions.

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