volkern_create_lead

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

With no annotations provided, the description carries the full burden. It discloses the key behavioral trait of upsert logic (create-or-update based on email), which is valuable beyond basic creation. However, it doesn't mention other important behaviors like required permissions, rate limits, what happens with duplicate non-email fields, or the response format.

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 perfectly concise with two sentences that each earn their place: the first states the primary purpose, the second adds crucial behavioral context. No wasted words, and the most important information (the upsert behavior) is front-loaded in the second sentence.

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?

For a mutation tool with 9 parameters, no annotations, and no output schema, the description is minimally adequate. It covers the core purpose and key behavior (upsert), but lacks information about permissions, error conditions, response format, or how it differs from similar tools like volkern_create_contact, leaving gaps in 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 schema already documents all 9 parameters thoroughly with descriptions, enums, and required fields. The description adds no parameter-specific information beyond what's in the schema, meeting the baseline for high coverage.

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 specific action ('Create a new lead') and resource ('in the CRM'), and distinguishes it from siblings by mentioning the unique upsert behavior ('If email already exists, updates the existing lead'), which differentiates it from tools like volkern_update_lead that presumably only update.

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 clear context for when to use this tool (creating leads, with upsert logic based on email), but doesn't explicitly state when not to use it or name alternatives like volkern_create_contact for contacts instead of leads, or volkern_update_lead for updates without creation.

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