browse_offers

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

With no annotations provided, the description carries the transparency burden. It discloses that all offers come live from the Freeplay API and specifies the content of the display. The operation is inherently read-only, and while it omits pagination details, these are covered in the schema descriptions.

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, front-loaded with the main action, and contains no unnecessary words. Every sentence earns its place.

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 simple browsing tool, the description covers the core purpose, data source, and displayed content. Pagination is implied via the page/page_size parameters in the schema, and the lack of an output schema is acceptable for a listing operation. It is sufficiently complete for an agent to use correctly.

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?

All five parameters have descriptive text in the input schema (100% coverage), so the description adds no extra parametric meaning. According to the rubric, this meets the baseline score of 3; the schema handles parameter semantics.

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 uses a specific verb 'browse' with the resource 'available offers' and clearly states what the tool shows: offer names, actions, earnings, and device requirements. This differentiates it from sibling tools like get_offer by focusing on the listing/browsing aspect.

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 clear context that this is for viewing offers users can complete to earn money, implying when to use it for browsing/listing. However, it does not explicitly mention alternatives or exclude usage for specific offer lookup, which would require get_offer.

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