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

Beyond annotations, it usefully discloses that prohibited content is refused, that the tool is non-custodial and never moves money, and that API key authentication is required. It does not contradict the annotations (non-destructive creation).

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 short and front-loads the core purpose. The remaining sentences each add relevant behavioral or safety context without unnecessary padding.

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 mutation tool with 15 parameters and no output schema, the description is far too thin. It omits essential parameter semantics and does not explain lifecycle fields like staged, milestones, or delivery configuration, leaving an agent under-equipped to call it 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?

Schema description coverage is only 20% across 15 parameters. The description only maps to the kind enum (sell vs buy) and adds no meaning for required fields such as category, delivery_method, staged, milestones, or the various delivery fields.

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 states a specific action and resource: 'Post a sell listing or a buy request (Need)'. It distinguishes the two modes via sell/buy, but does not differentiate from the sibling tool create_listing_from_x402.

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?

Usage is implied for creating sell listings or buy requests, and the Bearer auth requirement is noted. However, it gives no explicit guidance on when to prefer this over create_listing_from_x402 or other listing-related siblings.

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