search-flights

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It only states 'search for flights' and gives no information about read-only guarantees, side effects, authorization requirements, rate limits, or the nature of results. This is a significant gap for a tool with six required parameters.

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 ('search for flights'), but it is under-specifying rather than efficiently informative. A single vague phrase does not earn its place, and the structure provides no front-loaded useful details.

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 tool has six required parameters, no annotations, and no output schema, placing a high burden on the description to provide context. The description offers almost no beyond-schema value, leaving the agent uninformed about expected behavior, return format, or usage 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 100%, so all six parameters have descriptions in the schema itself. The tool description adds no additional parametric meaning beyond the schema, so it meets the baseline of 3.

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 for flights' identifies the core action and resource (flights), making its basic purpose clear. However, it lacks any specificity about scope, constraints, or what distinguishes it from potential sibling tools, so it is only minimally adequate.

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 guidance on when to use this tool versus alternatives like 'search-hotels-by-coordinates' or 'today'. There are no mentions of context, prerequisites, or exclusions, so the agent receives no decision support.

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