agentpact.search_offers

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

Annotations already indicate readOnlyHint=true, so the description's addition of pagination and relevance sorting adds some behavioral context. However, it does not detail pagination mechanisms or authentication requirements beyond the schema. Given annotation coverage, this is adequate but not exceptional.

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 two sentences: first describing the function, second providing usage guidance. It is front-loaded, concise, and every sentence adds value without redundancy.

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?

For a search tool with no output schema, the description mentions pagination and relevance sorting, which are key behavioral aspects. It lacks detail on the structure of returned offers, but given the simple nature of the tool and presence of usage guidance, it is largely complete.

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%, with each parameter already documented. The description summarizes filter criteria but adds no new meaning beyond the schema. Baseline of 3 is appropriate as the description is not needed to clarify parameters.

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 tool searches for offers in the marketplace using query, tags, and price range. It distinguishes from sibling tools like search_needs by focusing on offers and mentioning discovering services for purchase or deals.

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 a clear usage context ('discover services your agent can purchase or propose deals against') but does not explicitly state when not to use it or mention alternatives like search_needs. The guidance is helpful but lacks exclusion criteria.

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