create_prediction_with_history

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

With no annotations provided, the description carries full responsibility for disclosing behavioral traits. It only says 'Run a Flowise chatflow with conversation history' but fails to mention whether a prediction record is created, any side effects, authentication requirements, or what the response looks like. This is a black-box description for a potentially mutating operation.

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?

A single sentence with no filler, front-loading the verb and resource while highlighting the key differentiator (history). Every word earns its place, making it concise and easy to scan.

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 5 parameters, nested objects, and no output schema or annotations, the description is far too brief. It omits critical context such as return values, prerequisites (e.g., chatflow must exist), and how the conversation history is processed, leaving significant gaps for an agent to invoke it correctly.

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 provides descriptions for all 5 parameters, so the schema alone offers high coverage. The description adds minimal value beyond the schema, only linking 'conversation history' to the history parameter without extra detail on how it is used or formatted.

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'), the resource ('Flowise chatflow'), and the distinguishing feature ('with conversation history'), which differentiates it from siblings like create_prediction and create_prediction_with_files. The scope is specific and unambiguous.

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 conversation history is needed, but it does not explicitly guide the agent on when to choose this tool over its alternatives (e.g., create_prediction without history, or create_prediction_with_files). No exclusions or alternative tools are named, leaving the agent to infer the context.

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