fmod_system_message

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

The description explicitly states 'blocking' and 'popup dialog', which are important behavioral traits. However, with no annotations, it relies solely on this brief description. It does not mention return behavior, side effects, or conditions under which the popup may not appear.

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 plus a tag, which is concise and to the point. It front-loads the key action and behavior. However, it could be slightly expanded to cover parameter usage without losing conciseness.

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 simplicity (one parameter, no output schema, no annotations), the description provides the core purpose and a key behavioral trait. However, it lacks usage guidelines and parameter semantics, leaving gaps that could confuse an agent about when and how to use it.

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?

The parameter 'msg' has no description in the schema or the tool description. The description only states the tool logs a message but does not explain what the parameter represents (e.g., the content of the message, formats, or constraints). With 0% schema description coverage, the description fails to compensate.

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 'Logs a message in a popup dialog (blocking)', specifying the action (log), the output (popup dialog), and a key behavioral trait (blocking). This distinguishes it from siblings like fmod_system_print (likely console output) and other logging tools.

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 explicit guidance on when to use this tool versus alternatives like fmod_system_print or fmod_system_warn. The description implies it's for user-facing blocking messages, but does not state when to prefer it over other logging methods.

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