Create Lead

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

The description discloses the upsert behavior (update if email exists) which is beyond the simple 'create' annotation (readOnlyHint: false). It adds context about required fields and idempotency, but does not mention authentication, rate limits, or side effects. The description does not contradict annotations.

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 sentences long, directly states the main action and key constraint, with no extraneous information. It is front-loaded with the primary 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 the tool has 8 parameters and no output schema, the description lacks information about the return value (e.g., whether it returns the lead ID) and any potential errors. However, it covers the essential behavioral aspect (upsert). For a creation tool with moderate complexity, it is minimally adequate but has clear gaps.

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?

The schema has 100% description coverage, but the description adds value by clarifying the mutual requirement of email and phoneNumbers ('At least one must be provided'), which is not explicitly stated in the individual parameter descriptions. This aids in understanding the parameter relationship.

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', with additional nuance about upsert behavior. It distinguishes itself from siblings like hyros_update_lead by specifying that an existing lead with the same email will be updated.

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 a condition (at least one of email or phoneNumbers must be provided) but does not guide the agent on when to use this tool versus alternative tools such as hyros_update_lead or hyros_get_leads. No explicit when-to-use or when-not-to-use guidance is given.

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