Retrograde Periods

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

Annotations already mark the tool as readOnly, non-destructive, and idempotent. The description adds specifics about finding stations and mentions cost, but does not disclose any behavioral traits beyond what annotations provide. Adequate but not enhanced.

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 relatively concise but includes extraneous formatting like [Group: Calendar & Cycles] and [Cost:...]. While not verbose, it could be streamlined to focus on core functionality.

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 and 0% schema description coverage, the description lacks details about return format, possible planet IDs, ordering, pagination, or error conditions. Incomplete for an agent to fully understand the tool's behavior.

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?

Schema description coverage is 0%, so the description must compensate. It provides an example but does not explain that 'planetIds' is an array or what planet IDs represent (e.g., numbering scheme). The mismatch between 'planetId' in example and 'planetIds' in schema further reduces clarity.

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 it finds retrograde stations (direct, retrograde, stationary) for a planet within a date range. However, there is inconsistency: the description and example use singular 'planetId' while the schema defines 'planetIds' as an array, which may confuse an agent.

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 guidance on when to use this tool versus alternatives (e.g., stream_retrograde_alerts, webhooks_retrograde_start/end). The description only states what it does without any usage context.

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