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

With no annotations, the description carries the full behavioral load and does substantial work: it discloses that criteria are versioned and ride in the payload, that there is deliberately no composite score/stars/reliability index, and that 'unknown' and 'not_applicable' are distinct meaningful values rather than omissions. It stops short of stating read-only status or any rate/permission constraints.

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 prose is dense and partly redundant — the collateral/eth explanation appears twice in the body and again in the schema. The core idea (per-criterion venue data, no composite score) is front-loaded, but the middle paragraphs repeat themselves rather than advancing the reader.

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 read-only retrieval tool with no output schema, the description does explain the return shape (per-criterion cells with value and source across three pillars) and the collateral switch. Combined with 100% schema coverage, an agent has enough to call it correctly, though the exact payload fields are not enumerated.

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%, so the schema already documents all three parameters, and the collateral text in the description is nearly a verbatim duplicate of the schema field description. It adds some interpretive value ('the six tiles and books' for the eth case, mapping to the headline include), but the baseline of 3 holds when the schema does the heavy lifting.

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 resource and scope: it returns what is known about one venue, criterion by criterion, broken into the Price/Quality/Composition pillars with values and sources. That clearly separates it from list_venues (discovery) and compare_venues (multi-venue), even though it never names them explicitly.

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 only implied. It tells the agent to supply collateral: 'eth' for ether-secured credit and points to get_guide for SQ-V2/SQ-V3, but it never states when to reach for this tool instead of compare_venues or how it relates to list_venues. The routing context is thin.

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