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

The readOnlyHint annotation already establishes the safety profile, so the description's main contribution is enumerating what comes back (escrow balance, deadlines, dispute state, activity), which is genuinely useful since no output schema exists. It stops short of disclosing what 'your next move' or 'checks' concretely contain, how much activity history is returned, or what happens with an invalid or expired token.

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?

It is a single compact line with no padding, which is good, but the comma-spliced noun list without a leading verb makes it feel like an unedited field dump rather than front-loaded prose. Items like 'checks' and 'your next move' are too terse to land without context.

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 schema coverage and a readOnly annotation, the essentials for invocation are present, and the return-content list partially compensates for the missing output schema. Gaps remain around the meaning of ambiguous list items and token failure behavior, so it is adequate but not complete.

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?

Both parameters are fully documented in the schema, including the token's provenance (mm_create_deal or a ?k= link) and the deal_id format example. The description adds nothing about either parameter, so the schema does all the work and baseline 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?

The description is a bare noun list ('Current status, your next move, money in escrow, deadlines, checks, dispute and recent activity') with no verb or resource framing, so the read operation is only implied. It does signal that this is a read-only overview of a single deal rather than a mutation, which separates it loosely from action siblings, but phrases like 'checks' remain opaque.

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?

There is no when-to-use guidance and no mention of alternatives such as mm_get_funding_request or mm_get_payment_link, which also retrieve deal-related resources. The agent is left to infer that this is the general-purpose deal status lookup when coordination is needed.

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