start_optimization_session

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

With no annotations, the description details the entire internal process: reading state, running tests, scoring, analysing failures, writing prompts. It does not mention error handling or side effects on failure, but covers the main behavioral flow.

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 structured with prerequisites and numbered steps, front-loading the purpose. It is thorough but not excessively long; every sentence contributes value.

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 complexity and no output schema, the description fully explains prerequisites, internal steps, and follow-up actions. It references sibling tools and integrates the workflow context.

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?

Two of three parameters have schema descriptions (67% coverage). The description adds default values for threshold (70) and maxIterations (5), enhancing understanding 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 verb 'Run one optimization pass' on 'an existing workspace'. It distinguishes from sibling tool 'loop_optimization' by noting this is one iteration.

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 lists three prerequisites (do these first) and provides a clear after-action: user reviews, then call again or switch to loop_optimization. Also warns 'do NOT auto-apply'.

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