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

Beyond the annotations (readOnly=false, destructive=false, idempotent=false), the description discloses a critical behavioral trait: the request is staged and does nothing until a human approves it in Settings > MCP and execute_approved_action is called, with configurable and workflow-level approvals. This two-step approval gating is essential context the annotations do not convey.

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 approval disclosure is valuable and the text is front-loaded with usage, but the sentence 'Create deal.' merely restates the name and title without adding information. It is reasonably sized but contains at least one redundant line that does not earn its place.

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 mutation tool with a large nested payload, the description covers the high-stakes behavioral aspect (approval/deferred execution) well, and an output schema exists to explain returns. Its main shortfall is the absence of any guidance on the 'data' object's fields, which is significant given the complexity but partially offset by the output schema and application-side validation note.

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% and the single 'data' parameter is a large, undocumented nested object (~30 fields with enums like stage, source, assetType). The description only notes that 'required fields are validated by the application' and adds no field-level meaning, so it fails to compensate for the coverage gap on a complex payload.

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 pairs a clear verb ('Create') with the resource ('deal' / 'RetailHardHat deals records'), and the opening clause scopes it to the connected organization. It does not explicitly distinguish itself from update_deal or delete_deal, but the create semantics are self-evident from the name and verb.

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?

The phrase 'Use this when working with RetailHardHat deals records' is a weak usage hint that only implies context rather than stating when to create vs. update or list. No alternatives or exclusions are named, leaving the agent to infer that this is the creation path.

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