space.satellite

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

Discloses source (fresh Celestrak elements + SGP4) and return values (sub-point, speed, optional look angles). No annotations exist, so description carries full burden. Adequate but could mention data latency or limits.

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?

Single sentence, no redundancy, essential information front-loaded. Every part adds value.

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?

Captures core functionality and optional parameters, but omits explanation of altKm and at, and no return type structure. Given no output schema or annotations, more detail would be helpful.

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?

Explains noradId with example and lat/lon for observer position. But altKm and at (date-time) are not explained in description, and schema has no descriptions. Leaves ambiguity about optional parameters.

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?

Clearly states verb 'current position', specific resource 'any cataloged satellite by NORAD number', and distinguishes from siblings like space.body by focusing on satellites and providing an example (25544=ISS).

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?

Provides clear context: use for current satellite position with optional observer location for look angles. Includes an example NORAD ID. Does not explicitly exclude sibling tools, but usage is well implied.

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