Apply Optimization

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

Description adds context beyond annotations by noting the one-click requirement and caution against unvalidated changes, complementing the idempotentHint and destructiveHint with functional constraints.

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?

Three sentences are front-loaded with main purpose, then constraints, then guidance. Every sentence adds value without redundancy.

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?

For a 3-parameter tool with full schema coverage and no output schema, the description adequately explains what the tool does, its constraints, and appropriate usage 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?

Schema coverage is 100%, so baseline is 3. Description adds minimal extra meaning by giving examples for optimization_type and noting payload is an advanced override.

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?

Description clearly states the verb 'Apply' and resource 'one-click optimization recommendation to an agent', and distinguishes from sibling 'create_model_experiment' by specifying only works for one-click suggestions.

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 when to use (one-click optimizations) and when not (unvalidated changes), and recommends alternative 'create_model_experiment' if unsure about impact.

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