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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed-world scope, so the safety profile is covered. The description earns credit by disclosing what is actually returned (original values, cohort, problems, recordable terms, report impact) and adding a prompt-injection caveat about untrusted CRM content, going beyond the structured fields.

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?

The return contents are front-loaded before the security admonition, and the two-sentence structure is efficient. The field enumeration is slightly long but each item adds discriminative value for a tool with no output schema.

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 description usefully enumerates what is returned, and annotations carry the read-only/idempotent profile. The one residual gap is that it does not distinguish this call from get_deal_commercials, which an agent choosing among commercial-review tools would want.

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 50%: workspaceId is fully documented in the schema, while dealId has only a UUID pattern and no description. The phrase 'one deal you may view' weakly maps to dealId, so the description neither fully compensates for the gap nor leaves it wholly opaque.

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 ('Returns the pricing review details of one deal') and enumerates the payload contents. However, it never names or contrasts with close siblings like get_deal_commercials or list_commercial_review_queue, so the agent must infer the boundary from name alone.

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?

'One deal you may view' and 'Works also for a deal that already has saved pricing terms' imply permission scoping and that the deal need not be pre-save, which is useful. But there is no explicit when-to-use vs. when-to-use-get_deal_commercials guidance and no stated alternative, leaving usage implied rather than directed.

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