optimize_for_performance

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

With no annotations provided, the description bears full responsibility for disclosing behavioral traits. It only claims 'expert optimizations' and achieving 60fps but omits critical details: whether the tool modifies the input code destructively, the nature of optimizations applied, permissions required, or any limitations. This is a significant gap for a potentially mutative tool.

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 a single sentence, making it concise, but it lacks structure and is overly vague. Front-loading is adequate as it starts with the action, but the sentence is too brief to convey necessary detail.

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 (optimizing animation code) and the absence of an output schema or annotations, the description is insufficient. It does not explain return values, success criteria, error conditions, or scope of optimization. The 100% schema coverage partially compensates, but the description fails to provide a complete picture.

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 the baseline is 3. The description adds no extra meaning beyond the schema parameters. The param descriptions in the schema already explain 'GSAP animation code' and 'optimization target' with enums. The description's vague 'expert optimizations' does not enhance understanding of parameters.

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 optimizes animations for 60fps performance, but it uses the vague term 'any animation' while the input schema specifies GSAP animation code, creating a slight mismatch. The verb 'transform' and resource 'animation' are clear, and it distinguishes from siblings like 'debug_animation_issue' and 'create_production_pattern' by focusing on optimization.

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?

No guidance on when to use this tool versus alternatives like 'debug_animation_issue' or when not to use it. The description lacks context about prerequisites, such as needing a valid GSAP animation, or scenarios where it might be inappropriate (e.g., for non-GSAP animations).

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