fo_search_products_full

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

With no annotations, the description must fully disclose behavioral traits. It mentions the tool is 'slower' and provides 'richer data', but does not detail the extent of slowness, rate limits, or what other fields are in 'full details'. It adds some value but lacks comprehensive transparency.

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 with two sentences, front-loading the action and outcome. Every phrase is functional: 'Search FlexOffers product catalog with full details including discounts and sale flags' covers purpose and key features. No unnecessary words.

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?

Despite having 8 parameters and no output schema, the description is sparse. It does not explain what 'full details' entails, lacks guidance on parameter combinations or defaults, and doesn't address pagination or result handling. The missing behavioral and parameter context makes it incomplete for safe 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?

Schema coverage is 75%, so baseline is 3. The description does not add any parameter-specific information beyond the overall purpose. It fails to compensate for the two parameters (page, Country) that lack schema descriptions, limiting the agent's understanding of how to invoke the tool correctly.

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 the verb 'Search' and the resource 'FlexOffers product catalog'. It specifies that it provides 'full details including discounts and sale flags', and explicitly distinguishes the tool from its sibling 'fo_search_products' by noting it is slower but richer, ensuring the agent can select the right 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 provides guidance on when to use this tool: when richer data (discounts, sale flags) is needed and speed is less critical, as it notes 'Slower than fo_search_products but richer data'. However, it does not specify when to avoid using it or mention any prerequisites, missing some explicit guidance.

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