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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so safety profile is largely covered. The description adds real value beyond that by disclosing the PENDING initial state, the no-payment outcome, and the prerequisite workspace_key — but says nothing about idempotency, duplicate handling, or what happens to later approval.

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?

Two short sentences with the prerequisite front-loaded in parentheses and the outcome/approval path following. Every clause carries information; nothing is redundant filler.

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 10-parameter mutation with no output schema, the description covers lifecycle and the external approval gate but omits what the call returns (e.g., whether a deal id is produced and needed for approve_deal). Adequate to call it correctly, but incomplete about the handoff to the approval step.

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%, including the workspace_key provenance note, so the schema carries parameter semantics fully. The description repeats the workspace_key dependency but adds no meaning about the other nine fields (gci vs price+commission_pct, side normalization, referral fields), 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 description states a specific action and resource — enter a closed or closing deal, created in PENDING state — and implicitly separates it from the approval step by naming approve_deal. It stops just short of a crisp verb+resource framing ("record a deal"), but an agent can still tell this apart from approve_deal without opening the schema.

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 gives a clear usage context: the deal must be closed or closing, it lands as PENDING, nothing is paid, and the owner approves it in the app or via approve_deal. That effectively routes approval away from this tool, though it does not explicitly state when not to use it (e.g., for already-approved or paid deals).

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