fa_foresight_search

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

Annotations already indicate readonly and open-world behavior. The description adds that it uses Boolean query language and is predictive, plus warns about subscription limits. No contradiction with 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?

Two sentences, front-loaded with purpose, no unnecessary words. Highly efficient.

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?

As a search tool with pagination and no output schema, the description omits details about return format, pagination usage, or how predictions differ from standard search. Adequate but gaps remain.

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 covers 100% of parameters with descriptions. The description only mentions 'Boolean query language' which is already in the schema. No additional semantic 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?

Clearly states it's a predictive flight search using Boolean query language, and distinguishes itself from sibling fa_search_flights_advanced by noting it uses predicted data. The purpose is specific and unambiguous.

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?

Provides a note about premium subscription requirement and potential 402/403 errors, which guides usage. Compares to fa_search_flights_advanced, but does not explicitly state when to choose one over the other.

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