Move a deal

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

No annotations are provided, and the description only states the HTTP method and basic action. It does not disclose behavioral traits like required permissions, side effects, or return values, which are essential for a mutation tool.

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 description is concise but lacks structure. It includes technical details like the HTTP endpoint and tags that are already implied by the tool name, and the core purpose is stated in a single sentence without prioritization.

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 the absence of an output schema, annotations, and parameter documentation, the description fails to provide sufficient context for the agent to understand the tool's full behavior and requirements. The existence of many similar sibling tools further necessitates a more complete description.

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 0%, and the description adds no meaning to the parameters. It only mentions 'Body: application/json' without explaining the structure or fields like 'statusId' or 'previousDealId', which are critical for correct invocation.

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 states the action ('move') and the resource ('a deal within the funnel'), making its purpose understandable. However, it does not differentiate from sibling tools like 'weeek_move_a_attached_to_the_deal_task' or 'weeek_update_a_deal', which have overlapping functionality.

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 description provides no guidance on when to use this tool versus alternatives, such as other move or update tools. No explicit context or exclusions are mentioned, leaving the agent to infer usage from the tool name alone.

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