update-menu

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

No annotations are provided, and the description doesn't disclose any behavioral traits beyond the act of updating. It doesn't mention permissions, side effects, reversibility, or return behavior, which is a significant gap for a mutation tool.

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, but it's under-specified. While it's concise, it doesn't earn its place by providing necessary detail; it's more of a placeholder.

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?

With no annotations, no output schema, a flexible updates object, and a vague description, the tool is severely incomplete. The agent cannot safely invoke this tool without additional knowledge.

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 schema has 0% description coverage, and the description adds no meaning to menu_id or updates. The updates object is entirely opaque with additionalProperties, and the description doesn't hint at valid fields or structure.

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 uses 'Update' as a specific verb and 'UI menu' as the resource, clearly distinguishing it from sibling tools like create-menu and delete-menu. However, it lacks scope detail, so it's clear but minimal.

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 is provided on when to use this tool versus alternatives. The description doesn't mention prerequisites, context, or exclusions, leaving the agent without decision support.

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