fmod_ui_sizePolicy

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

The description explains the behavioral concept (how the widget consumes space and reacts to space changes). However, with no annotations, it fails to disclose valid enumeration values, side effects of setting, or whether the operation is destructive. Schema coverage helps slightly but the description does not enumerate values.

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 two concise sentences, front-loaded with the tool's nature as an enumeration and immediate behavioral explanation. No unnecessary words.

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 simple enumeration tool with no output schema and incomplete annotations, the description adequately explains the concept but misses typical usage patterns and valid value constraints, making it only moderately complete.

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 a clear description for the 'value' parameter. The tool description adds no additional meaning beyond the schema, so a baseline score of 3 is appropriate.

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 that this tool corresponds to the size policy enumeration for a widget, explaining what size policy determines. It distinguishes from sibling UI property tools by its specific property name, but does not explicitly differentiate from similar enumeration tools like alignment or orientation.

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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention context or prerequisites, leaving the agent to infer usage from the sibling tool set (all UI-related).

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