Optimize performance

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

Description explains default behavior (report + suggestions) and modify behavior (lower resolution, scale). Annotations already indicate read-write, so description adds value. Could mention reversibility, but overall transparent.

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, no filler. Front-loaded main purpose and usage advice.

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 (4 params, no output schema, annotations present), the description is complete: covers what it does, how to use, alternatives, and parameter roles.

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% with good parameter descriptions. Description adds workflow context and explains how 'scale' is used, enhancing schema. No redundancy.

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?

Clearly states the tool scans for cook-time bottlenecks and optionally fixes them. Distinguishes itself from sibling 'get_td_performance' by contrasting 'just want the numbers' vs 'act on them'.

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 advises to run get_td_performance first if only numbers are needed, then use this tool to act. Describes default reporting mode and apply:true modification mode.

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