create_prediction_with_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. It mentions 'run' and 'capture' but does not explain side effects (e.g., what prediction record is created, whether data persists), permissions, return value, or what 'capture' concretely does. This is a significant gap for a tool that likely mutates state.

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 11 words, front-loaded with the action. Every word is purposeful and there is no fluff. It is appropriately concise for a tool whose parameters are well-documented in the schema.

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?

The tool has 5 parameters, no annotations, no output schema, and several sibling tools. The description is too minimal to be complete: it doesn't clarify what a 'prediction' means, what happens with the lead email, whether chatId is needed for context, or what the response contains. The schema covers parameters but not the broader usage context or behavior.

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 input schema has 100% description coverage for all parameters, so the baseline is 3. The description adds no extra meaning beyond the schema; for example, 'capture a lead email' reflects the leadEmail parameter but does not elaborate on how it's used or any constraints beyond the 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: 'Run a Flowise chatflow and capture a lead email for the conversation.' This includes a specific verb+resource and explicitly distinguishes from sibling tools like create_prediction or create_prediction_with_history by highlighting the lead email capture.

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 usage when running a chatflow while needing to capture a lead email, but it does not explicitly mention alternatives or exclusions. Given the sibling tools, there is no direct guidance on when to choose this over create_prediction or other variants.

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