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

With no annotations provided, the description discloses the authentication requirement (needs a bearer) and confirms read-only operation (no write scope). It also notes the default active=True and limit<=200. However, it does not mention pagination beyond offset/limit, return format, error handling, or rate limits, leaving some behavioral gaps.

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 covering purpose, parameters, defaults, and auth. It is front-loaded with the primary purpose and packs significant information efficiently 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?

Given the output schema exists, the description covers essential aspects: kind selection, parameter list with defaults, limit constraint, auth, and read-only status. It does not explain every parameter's semantics in depth, but for a browse tool with an output schema, the coverage is adequate 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?

Schema description coverage is 0%, so the description must compensate. It lists the query parameters (frontier, resource_type, oracle_verified, active, limit, offset, sort) and gives some defaults and constraints (limit<=200, default 50, sort default 'price_asc'). It adds context beyond the schema names but does not explain the meaning of frontier or resource_type, so compensation is partial.

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 it browses the RAREEAI marketplace and distinguishes two kinds (providers and oracles). It uses the verb 'browse' with a specific resource, making the purpose obvious. It does not explicitly compare to sibling tools like market_accept or market_request, but the contrast is implied.

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 usage context: which kind to specify, the available query parameters, defaults, and the limit constraint. It implicitly indicates this is the read/browse tool versus the action tools, though it does not explicitly state when to use it over alternatives.

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