space.launches

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions return fields but fails to state that the operation is read-only, lacks authentication requirements, rate limits, or other side effects. The description is insufficient for a tool with no annotations.

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 a single, well-structured sentence that immediately states the purpose. It lists key details (parameters, search capability, return fields) without any filler. Every part 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?

The description covers the tool's purpose, input parameters, and return fields. Given the absence of an output schema and annotations, it provides adequate context for a list-type tool. It could mention pagination behavior (limit/offset) or ordering, but overall it's mostly complete.

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 description adds meaning to the 'search' parameter by specifying it can filter by rocket/provider/mission, which is not in the schema. For 'when', it clarifies the enum values. For 'limit' and 'offset', no extra info, but the schema already provides defaults and ranges. Overall, the description adds value beyond the schema.

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 lists 'Upcoming or recent orbital rocket launches' and specifies the resource (Launch Library 2). It distinguishes from sibling space tools like space.body, space.satellite, etc., by focusing on launches.

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 provides the when parameter (upcoming/previous) and optional search, implying use cases. However, it does not explicitly guide when to use this tool versus alternatives, nor mention any exclusions or prerequisites.

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