set_anti_aliasing

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

No annotations are provided, so the description carries full burden. It does not disclose that this is a mutation operation, potential side effects (e.g., immediate visual change), or permission requirements. The description only states 'configure' without behavioral context.

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?

One sentence with three acronyms. Highly concise, front-loaded with the verb and resource. Every word earns its place. No filler text.

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 3 parameters and no output schema or annotations, the description is too brief. It does not explain the tool's effect on the rendering pipeline, whether it requires a project to be open, or what the outcome of setting these options is. More context is needed for safe usage.

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 description coverage is 100%, so baseline is 3. The description lists the three parameter types but adds no meaning beyond the schema's existing descriptions (e.g., 'Enable/disable TAA'). No additional syntax or usage hints are provided.

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 action ('configure') and resource ('anti-aliasing settings') and lists common types (MSAA, FXAA, TAA). It is specific and distinguishes from other rendering tools. However, the scope (global vs scene-specific) is ambiguous.

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, when not to, or alternatives. The description simply states what it does, leaving the agent to infer usage context. For a configuration tool, prerequisites or impact on rendering could be mentioned.

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