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

The description provides rich behavioral context beyond annotations, detailing side effects like stopping public marketplace feeds, stopping boosts, and notifying saved members. It clearly defines the scope ('under scope 'mine'') and limitations (does not edit or delete).

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 tool definition is densely packed with information, but it is highly efficient. The structure is logical: definition -> finding ID -> mechanics -> required workflow -> limitations. Every sentence serves a critical, non-redundant purpose.

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?

Given that this is a complex mutation tool with an operational workflow requirement, the definition is extremely complete. It covers the what, why, how, safety protocol, and boundary conditions, leaving the agent fully equipped to use it correctly.

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?

Although schema coverage is 100%, the description adds value by explicitly stating that the `deal_id` must be sourced from `connections_deals_list` scope 'mine'. This adds necessary context to parameter usage that transcends basic schema definition.

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 clearly defines the purpose: to 'close, wrap up or take down a deal.' Crucially, it distinguishes this function from `connections_deal_update` by focusing on status transition (setting it to 'closed') rather than modifying other attributes.

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 provides explicit 'when to use' guidance ('when the member asks to close, wrap up or take down a deal that is done'). Furthermore, it mandates a specific operational workflow: requiring the agent to use `dry_run` true first and confirm with the member before execution.

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