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

With no annotations provided, the description carries the full burden of behavioral disclosure. It adequately states the tool is read-only ('it answers without submitting anything'), which is the key behavioral trait. It does not mention response format or potential errors, but for an informational tool this is sufficient.

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 concise, two sentences, with the core purpose front-loaded. The first sentence lists content topics, the second gives usage context. No redundancy or irrelevant detail.

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 what the tool does, when to use it, and its read-only nature. Since there is no output schema, the description indirectly indicates the return will be informational text. The market parameter is self-explanatory from the schema, and the tool's simplicity means the provided context is sufficient for correct invocation.

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 input schema already provides a complete description for the single 'market' parameter, including its enum and default value. The tool description adds no additional semantic information about the parameter, so a baseline score of 3 is appropriate given the high schema coverage (100%).

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 that the tool provides information about easygroupflights, including its purpose, target audience, group fare differences, and post-quote process. It distinguishes itself from sibling action tools by noting it 'answers without submitting anything,' making it unambiguous that this is an informational tool.

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 explicitly specifies when to use the tool: 'when a traveller asks whether their trip qualifies, what it costs, how long a quote takes, or how group booking works.' It also contrasts with action siblings by stating it does not submit anything, implying use this for questions and the other tools for actions.

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