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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, so safety is covered. The description adds that view access is gated on a status_key issued at creation, which is genuinely useful context. It does not disclose what happens on an invalid/mismatched key or how much 'history' is returned.

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?

A single, front-loaded sentence with no wasted words. The primary resource (status/history) comes first and the identifier conventions are parenthetically appended.

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 two-parameter read tool with full annotations, the description covers what the tool returns (status and history) and where the required inputs come from. Lacking an output schema, it could say more about the shape of 'history' and failure behavior, but nothing essential to invoking it 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 0%, so the description must carry both parameters. It does add meaning for both: id carries an object-type prefix (d_ deal vs w_ watch) and status_key is a credential obtained at creation time. It still gives no format or validation detail for status_key, so compensation is partial.

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 action: retrieve the status and history of a brokerage deal or watch. The d_…/w_… prefix convention lets an agent distinguish which object type the id refers to. It is clear on its own, though it doesn't explicitly name the mutating siblings (watch_domain, request_acquisition) that create these records.

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 implied rather than stated: it tells you the call requires an id and status_key 'returned when it was created', which is a precondition. There is no explicit when-to-use vs. when-not guidance and no named alternatives, so the agent must infer that this is the read counterpart to the creation tools.

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