create_or_update_lead

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The description states 'create or update' but does not explain how the tool determines whether to create or update (e.g., matching criteria, what fields trigger an update). It also does not disclose side effects, required permissions, or whether the operation is idempotent. This is a significant gap 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 a single sentence of 13 words, which is concise and front-loaded. However, it could be more informative by adding a brief note on update behavior or matching criteria without sacrificing conciseness.

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 tool has 12 parameters, no output schema, and no annotations, the description is minimally adequate. It tells the core function but does not explain return values, how existing leads are matched, or how to handle errors. For a complex tool, more detail is needed for full completeness.

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 100%, so the baseline is 3. The description does not add any additional meaning beyond the schema; it does not elaborate on parameter behavior, such as how customFields work or how the tool identifies existing leads. The description adds no value over the structured schema.

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: 'Create a new lead or update an existing lead in a specified audience'. It specifies the verb (create/update), the resource (lead), and the context (audience). This distinguishes it from sibling tools like 'search_lead', 'remove_lead_from_audiences', and 'update_lead_status'.

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 implies when to use the tool (to create or update a lead) but provides no explicit guidance on when not to use it or alternatives. For example, it does not clarify when to use this tool over 'update_lead_status' or 'search_lead'. The usage context is implied, but no exclusions or alternative tools are mentioned.

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