create_lead_for_existing_client

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

No annotations provided, so description carries the burden. Explains the lead workflow (Lead -> Proposal -> Schedule -> Complete -> Invoice), default stage, and that `client_id` is numeric. Does not mention output or side effects, but overall transparent for a creation 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?

Well-structured with bullet-like points. Every sentence adds value; front-loaded with main purpose. Could be slightly shorter, but remains efficient.

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?

With 7 parameters, no schema description, and no annotations, the description adequately covers the core workflow and prerequisites. However, lacks explanation for several optional parameters and does not reference the output schema or `list_custom_inputs` for extra 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 0%, so description must compensate. Explains `client_id`, `operation_id`, and `visit_stage_id` with context. However, `name`, `tags`, `notes`, and `sales_rep_id` are left undocumented, leaving gaps.

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?

Clearly states 'Create a lead (Job) for an existing client already in SingleOps' with specific verb and resource. Distinguishes from sibling tool `create_lead_with_new_client` by emphasizing the client must exist.

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?

Explicitly instructs to use after `search_clients_by_email` or `search_clients_by_phone`, and to look up `operation_id` via `list_operations`. Provides workflow context and warns about `client_id` type, making when-to-use clear.

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