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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds nothing behavioral beyond that — no auth expectations beyond the token param, no indication of what happens if the deal path is missing, no freshness or caching notes. Listing the returned fields does give some sense of scope, so this is not a 1.

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 fragment with no filler, but the content is an unstructured list of return fields rather than a front-loaded statement of purpose. It is terse but poorly structured as a tool definition.

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?

With no output schema, the enumeration of returned data (parties, agreed version, deliveries, payments, ratings) is genuinely useful for an agent deciding whether this answers its question, and the annotations cover the safety profile. What is missing is any statement of the operation itself and how it relates to payment_status, so it is only minimally 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?

Schema description coverage is 100% — path, workspace_id and api_token are each documented in the schema, including the token-header alternative. The description adds no parameter-level meaning beyond that, so the 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 name and field list make it inferable that this reads a deal's status, but the description is a bare noun phrase with no verb, so the agent must infer the action. It also does not distinguish itself from adjacent siblings like payment_status, reputation or read_file, which plausibly overlap with the payments and ratings content described here.

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 at all: no statement of prerequisites, no indication of when this is preferred over payment_status or read_file, and no exclusions. The agent is left to infer usage entirely from the tool name.

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