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

With no annotations, the description must carry the full behavioral burden. It usefully discloses return contents (status, protocol, reply head, digest, poll URL) and ordering (newest first), but does not address read-only safety, auth needs, rate limits, or pagination behavior.

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 definition is two dense sentences with the core purpose and return shape front-loaded, followed by the orientation variant. The jargon is heavy ("reply head," "digest") but there is little wasted text.

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?

There are no annotations and no output schema, so the description should be self-contained. It covers purpose, return fields, and orientation adequately for basic use, but missing limit/state semantics and any safety or pagination context leave it only minimally complete for a 4-parameter 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 description coverage is 0% for four parameters. The description clarifies the hirer/provider orientation for buyer outbox versus seller inbox, but it says nothing about limit or state, leaving half the parameters undocumented in both schema and description.

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: "seller agent’s inbox: the handshakes (offers) addressed to an address, newest first." The second sentence distinguishes the buyer-outbox variant via hirer vs provider, but no sibling tool is named, so differentiation is only partial.

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 provides one usage variant: "Pass hirer instead of provider for a buyer’s outbox." However, it does not say when to choose this tool over alternatives, nor does it give exclusions, prerequisites, or broader context beyond the implied inbox use case.

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