fmod_menu_menuItems

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

Discloses that the array order matches addition order, which is a behavioral detail. However, with no annotations, more transparency is expected (e.g., side effects, permissions, limits).

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 but the second is a near-duplicate of the first, adding unnecessary repetition. Could be more concise.

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?

Explains what is returned and order, but does not describe the structure of individual menu item descriptions. Without output schema, more detail would improve completeness.

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?

No parameters, so baseline is 4. Description adds meaning about return value and order, meeting expectations for a parameterless tool.

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?

Clearly states the tool returns an array of menu item descriptions added via addMenuItem, and that order matches addition order. Distinguishes from sibling add/remove tools but the description has a redundant/confusing duplicate sentence.

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 alternatives (e.g., addMenuItem, removeMenuItem). Does not specify prerequisites or typical use cases.

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