createDeal

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

The description hints at behavioral expectations by stating 'FUB expects peopleIds (array) and price (number)', implying these are strongly recommended even if not required by the schema. However, with no annotations, more detail on side effects, permissions, or error handling is needed.

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 two short sentences, front-loaded with the key action, and every sentence adds value. No extraneous information.

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 16 parameters, no output schema, and no annotations, the description is severely lacking. It does not explain return values, error conditions, prerequisites (e.g., deal ownership, pipeline context), or behavior for optional versus required fields.

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 50% (8 of 16 parameters have descriptions). The description only adds detail for peopleIds and price, which are already described in the schema. It does not compensate for the 8 undocumented parameters.

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 'Create a deal', providing a specific verb and resource. It distinguishes from siblings like createDealAttachment or updateDeal, and adds expectations about peopleIds and price.

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 does not specify when to use this tool versus alternatives such as updateDeal or other create tools. No context on when not to use it is provided.

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