create_lead_obo

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

No annotations are provided, so the description carries the full burden. It discloses the key behavioral trait of disabling duplicate checking, which is critical. However, it does not mention other potential behaviors (e.g., creation always succeeds, possible errors, or what happens with existing duplicates).

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 concise sentence of 16 words that front-loads the key differentiator 'duplicate checking disabled' and the use case. Every word is necessary and contributes to the 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 9 parameters with no descriptions and no usage guidance beyond the purpose, the description is incomplete for an agent to correctly invoke the tool. The output schema exists but does not mitigate the lack of parameter semantics. The description does not explain how to fill parameters or what to expect after creation.

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%, yet the description provides no additional meaning for any of the 9 parameters. The parameter names are somewhat self-explanatory, but terms like 'lead_provider', 'summary', and 'case_type' could benefit from clarification. The description fails to compensate for the lack of schema descriptions.

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 verb 'Create' and the resource 'lead', and explicitly differentiates this tool by specifying 'duplicate checking disabled' and the use case 'On-Behalf-Of cases'. This distinguishes it from sibling tools like 'create_lead' and 'create_lead_full'.

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 context for when to use this tool: 'for On-Behalf-Of cases where the same contact has multiple matters'. It implies that duplicate checking is a distinguishing factor, but does not explicitly state when not to use it or mention alternatives.

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