get_otc_offers

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

No annotations exist, so the description carries the full burden. It discloses what is returned (token details, prices, status), which is useful, but says nothing about pagination behavior despite page/pageSize params, nor about auth requirements or rate limits. Partial disclosure only.

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 tightly written sentences with the resource and scope front-loaded; no filler and every clause carries information about what the tool returns.

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 list tool with 5 optional params and no output schema, the description covers the return payload at a high level but omits pagination mechanics and how filters combine, leaving gaps an agent would need to close by trial. Adequate but not 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%, so the schema already documents all five optional filters including defaults and bounds. The description adds no syntax or filter-interaction detail beyond that, which is the expected baseline when the schema does the work.

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 and resource (get OTC marketplace offers) plus domain (Cardano) and scope (peer-to-peer trading offers). An agent can distinguish it from create_otc_offer or fill_otc_offer, but it never explicitly contrasts with get_my_otc_offers or get_otc_offer_by_id, so the differentiation stays inferential.

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?

No when-to-use guidance, no exclusions, and no alternatives named. With five closely related OTC siblings (get_my_otc_offers, get_otc_offer_by_id, create/fill/cancel), the routing burden is left entirely to the agent's inference from the name.

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