get_next_pass

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

With no annotations provided, the description carries the behavioral disclosure burden. It does well by indicating this is a read-only information getter and explicitly stating that it returns None when no future passes exist, which is an important edge case.

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 two short sentences with no fluff. The main purpose is front-loaded, and the second sentence adds a meaningful edge-case behavior. Every word earns its place.

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?

For a zero-argument read-only tool, the description is mostly sufficient, but there is no output schema and the description never explains what 'information' actually includes. An agent may not know what fields or structure the returned pass information will have, which is a meaningful gap.

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?

The tool has no parameters, so there is no parameter-level semantics to document. The baseline for zero-parameter tools is 4, and the description correctly needs no parameter explanation.

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 operation: get information about the next upcoming satellite pass. It is distinguishable from get_all_passes because it explicitly targets only the next pass, and the None edge case makes the behavior more concrete.

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 gives clear context for when to use the tool: when information about the next upcoming pass is needed. It doesn't explicitly mention alternatives like get_all_passes, but the 'next upcoming' wording implies a natural contrast with getting all passes.

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