altair_run_operator_chain

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

No annotations provided, so description carries full burden. It discloses the need to write results via write_csv and implies the tool executes arbitrary graphs, which could have side effects. Missing details on error handling or performance, but sufficient for typical usage.

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?

Concise two-sentence description that front-loads 'ADVANCED / escape hatch' to set expectations. Every sentence adds value: purpose, when to use, tip, requirement. No wasted words.

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's complexity (nested objects, no output schema, no annotations), the description provides enough context: purpose, usage guidance, a key requirement, and a practical tip. It does not explain the return value, but the write_csv instruction implies the result is in the file. Overall, well-rounded.

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%, but description adds context by mentioning 'operator class keys, parameters, and port-level connections' and the tip about Export Process. However, it does not detail each parameter structure beyond what schema provides, leaving some interpretation for agents.

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 it is an advanced escape hatch to run arbitrary operator graphs, distinguishing it from dedicated sibling tools by listing examples like DBSCAN, Hugging Face, etc. The verb 'run' and resource 'operator graph' are specific.

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 says 'Use this for operators not covered by the dedicated tools' and provides a practical tip on exporting from Altair AI Studio. Also states a critical requirement: the graph must end with write_csv to an absolute path.

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