get_launch_history

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

The description goes beyond the simple annotations by revealing the data source ('FAA/GCAT database') and the specific fields included in the output (vehicle type, launch site, outcome, date). This context is vital for the agent to evaluate the relevance of the results.

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 extremely concise, with two sentences that deliver maximum value. The first sentence establishes the purpose, and the second details the data source and key output fields.

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 is highly complete for its function. It defines the input requirement (entity_id) and characterizes the result (data source, specific fields returned), allowing an agent to make high-quality decisions without an output schema.

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?

Since schema coverage is 100%, the baseline is high. The description adds value by explicitly stating that 'entity_id' is required and that 'vehicle' functions as a filter, providing practical usage semantics that complements 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 uses the specific verb 'Get' and clearly identifies the resource ('launch history for a space entity'). This is highly specific and immediately informs the agent of the tool's function.

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 no context for when this tool should be used versus alternatives, nor does it specify any prerequisites or exclusion criteria for its use.

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