fmod_ui_alignment

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

With no annotations, the description does not disclose behavioral traits such as whether the operation is destructive, idempotent, or requires specific permissions. It only calls it an enumeration, omitting the fact that setting a value modifies the alignment property.

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 concise at one sentence, but the cryptic notation '[property · ui.alignment]' reduces clarity. It could be restructured to list possible values or provide a clearer link to the property.

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 tool with one parameter and no output schema, the description should clearly explain that it reads or sets the alignment property. It fails to list possible enumeration values or explain the property path, leaving the agent underinformed.

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% and the parameter description in the schema is clear. The tool description does not add further meaning beyond what the schema provides, so baseline 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 states it is an enumeration for alignment within a layout widget, which conveys the basic purpose. However, it does not explicitly state that this tool can read or set the alignment property, and the reference to '[property · ui.alignment]' is cryptic. It distinguishes from other ui_* tools by topic but not clearly.

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 vs. siblings like fmod_ui_orientation or fmod_ui_sizePolicy. The description does not clarify when to read vs. set, nor does it mention any prerequisites or context.

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