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

Beyond the readOnly/idempotent annotations, it discloses substantive behavior: the log is visible to both buyer and seller, bound deals expose the other side's email in contact and in the log and should be given to the person, and seller_idle appears when a deal waits on the seller after buyer approval. These privacy and state behaviors are not captured by annotations, though the phrasing is cryptic.

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 with/without distinction is front-loaded, which helps. However, the remaining sentences are dense, run-on, and rely on unexplained terms like seller_idle, so the description is harder to parse than its length warrants.

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?

It covers both query modes, the privacy behavior around contact emails, and the relationship to market_wait. With an output schema and fully described parameters, the remaining omissions (ordering, pagination) are minor for a read-only log tool.

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 baseline is 3, but the description adds real meaning by explaining that deal_id switches the tool between a single-deal log and a person-level view of deals, listings, and questions. It does not elaborate on owner_key, but the schema already describes it fully.

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 names the resource (the deal log) and specifies two distinct modes: one deal's log with a deal_id, and the person's deals/listings/questions without one. It also distinguishes itself from market_wait, though the prose is elliptical and the primary verb ('read'/'return') is only implied rather than stated.

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?

It clearly separates usage by parameter: with deal_id for a single deal's log, without for the person's broader deals and questions. It also explicitly contrasts itself with market_wait, noting that a wait does not surface buyers' questions, which gives an agent a concrete routing rule, though no explicit 'do not use' cases are stated.

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