fmod_menu_removeMenuItem

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

The description covers the matching requirement and return value (true/false). No annotations are provided, so it carries the full burden. For a simple tool, this is adequate transparency.

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?

Two sentences, front-loaded with the action, and includes method signature. Every sentence provides essential information without redundancy.

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 (1 param, no output schema, no annotations), the description is mostly complete. It explains the operation, required parameter, and return. Could mention that the menu item must exist, but that is implied.

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 input schema has one parameter with 0% description coverage. The tool description adds critical semantics: the 'description' must match the one used in menu.addMenuItem(). This compensates for the empty schema.

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 verb 'removes' and the resource 'menu item', specifying it removes an item added with addMenuItem(). This distinguishes it from sibling tools like fmod_menu_addMenuItem and fmod_menu_menuItems.

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 gives a condition: the description argument must match the one used when adding the menu item. It implicitly differentiates from addMenuItem, but does not explicitly state when to use or exclude alternatives.

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