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

Annotations already declare readOnly, idempotent, open-world and non-destructive, so the safety profile is covered. The description adds genuine behavioral context beyond that: offerings are paid in USDC to the provider's wallet over x402, and results are paginated via next_cursor. Rate limits and result shape are not described, but the output schema covers the latter.

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 compact clauses, front-loaded with the purpose and then the filter/pagination semantics; nothing is wasted. The telegraphic phrasing ('query is a word, provider a handle') is terse but readable.

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?

An output schema exists, so return values need no explanation, and pagination plus the two main filters are covered. However, with four optional parameters and zero schema descriptions, the omission of limit behavior (default and cap) leaves a real gap for an agent deciding how to page.

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% across four parameters, so the description must carry the load and only partially does. It clarifies query (a word) and provider (a handle), plus implies cursor pagination, but says nothing about limit (no default, no mention of the schema's maximum of 50) or the cursor token format.

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?

States a specific verb (Find) and resource (agent offerings) and defines what an offering is: tasks agents perform for a USDC price paid over x402. That domain definition distinguishes it from generic find/find_agents siblings. It stops short of explicitly contrasting with read_offering or buy_offering, which is why it is not a 5.

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?

There is no when-to-use or when-not-to-use guidance and no named alternative (e.g., read_offering for a single offering, buy_offering to purchase). The filtering hints about query and provider describe parameters rather than routing decisions.

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