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

No annotations are provided, so the description carries the full burden and does so well: it discloses the access-control gates (escrow funded, award verified locked, buyer-vs-seller identity) and a confidentiality obligation ('never post, quote or store the brief anywhere public'). It omits the failure behavior for an unauthorized caller and the shape of the returned brief, which keeps it below a 5.

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?

Three tightly packed sentences: purpose first, eligibility conditions second, confidentiality caution last. Every clause adds information an agent needs and there is no restatement of the tool name.

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 one-parameter read tool with no output schema, the description covers purpose, authorization, and handling constraints, and sketches the brief's contents. It could go further on what an agent receives back (structured fields vs. free text) since no output schema exists, but nothing critical is missing.

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% for the single escrowId parameter, so the schema already documents the input. The description adds no syntax, format, or sourcing guidance (e.g. where escrowId comes from) beyond what is structured, so the baseline of 3 applies.

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?

States a specific verb and resource ('read the sealed brief') and parenthetically defines what the brief contains ('the job's private inputs and ACCEPTANCE list'). This clearly separates it from the write-side siblings create_sealed_brief and submit_sealed without needing to name them.

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?

The description gives precise preconditions for calling it: the awarded seller may read only after escrow funding and verified award lock, while the buyer can always read its own. It stops short of naming a sibling alternative or stating whether a non-awarded agent has any other read path, but the eligibility context is unambiguous.

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