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

No annotations are provided, so the description carries the full burden for behavioral disclosure. It only states what the tool is about, not what it does, what side effects it might have, what data it returns, or whether it performs reads/writes. 'Order book' hints at reading market depth but doesn't confirm the behavior, rate limits, or response shape.

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 extremely short—six words plus a title fragment. It is concise and wastes no words, but the brevity comes at the cost of substance. As a structural rating, it is front-loaded and readable, though the content is under-specified.

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 tool with no annotations, no output schema, and a highly ambiguous domain shared by many sibling tools, the description is severely incomplete. It doesn't state the action, return type, or expected input format. An agent has no way to invoke this correctly beyond guessing from the name.

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 coverage is 100%—both params have descriptions ('Asset to process' and 'Token to process'). However, the descriptions are generic and add only marginal meaning. The tool description itself doesn't elaborate on how 'asset' and 'token' relate to a Polymarket CLOB order book, leaving ambiguity about which identifier goes in which parameter. Baseline is 3 because schema covers documented fields, but the description fails to add value.

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 'Poly CLOB: Polymarket CLOB order book.' is a noun phrase, not a clear verb+resource statement. It identifies the domain (Polymarket CLOB) but doesn't state what the tool does with it—does it fetch the order book, place orders, or manage positions? The name 'x402-poly-clob' isn't disambiguated from siblings like poly-depth, polymarket-scan, or poly-price.

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 guidance on when to use this tool versus alternatives. The sibling list includes many Polymarket-related tools (poly-depth, polymarket-odds, poly-price, poly-markets, poly-volume, poly-walls) that likely overlap in domain, but the description offers no selection criteria. An agent cannot determine whether to call this for a depth query, a price query, or something else.

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