search_launches

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

No annotations are provided, so the description carries full burden. It lacks disclosure of behavioral traits such as pagination details, sorting behavior, response format, or rate limits. The main description is minimal and does not compensate for the missing 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 main description is a single concise sentence that front-loads the tool's purpose. It is appropriately sized for a simple search tool, though additional context could be included without sacrificing conciseness.

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 the absence of annotations and output schema, the description is too brief. It does not explain pagination, default sorting, response structure, or other contextual details needed for correct invocation. The parameter descriptions help but do not fully compensate for the lack of high-level context.

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 high (83%), so baseline is 3. The description adds significant meaning to the rql parameter by explaining syntax, operators, and field examples. However, it does not describe the sort parameter, and the overall parameter semantics benefit from the schema descriptions but are not fully enhanced by the main description.

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 'Search launches by AQL query.' clearly states the tool's action (search) and resource (launches) with a specific filter language (AQL). It distinguishes from siblings like list_launches (no filtering) and search_test_cases (different resource).

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 implies use for filtered searching via AQL but does not explicitly state when to use this tool over alternatives like list_launches or get_launch. No when-not or exclusion criteria are provided.

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