run_slx

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

Describes the execution flow (creates RunSession, polls, returns results) and default behavior for task_titles. No annotations are provided, so the description carries the full burden; it is fairly comprehensive but could mention any required permissions or rate limits.

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 well-structured with sections but slightly wordy; all sentences provide value and are front-loaded with the core action.

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 full parameter descriptions and the existence of an output schema (context signals), the description covers usage, behavior, and return results, making it sufficiently complete for an agent.

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?

Despite 100% schema coverage, the description adds meaningful context beyond the schema: examples for slx_name and workspace_name, explicit default and format for task_titles, and explanation for runtime_var_overrides.

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 tool runs an existing SLX's runbook tasks, distinguishing it from ad-hoc script tools (run_script/run_script_and_wait) and the search-only workspace_chat tool.

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?

Provides explicit when-to-use (health checks, troubleshooting existing SLX) and when-not-to-use (ad-hoc scripts), including direct references to alternative tools.

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