eda_sys_header_menu_replace_header_menus

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

No annotations are present, so the description must disclose behavior. It only says 'replace' and '替换顶部菜单数据' (replace top menu data), which is essentially the same as the name. It does not mention side effects, destructive nature, return value, or any operational details.

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 extremely concise, consisting of a code signature and a short Chinese phrase. It is efficient but lacks explanatory structure; it reads more like a header than a description.

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 tool with a generic args array and no output schema, the description is highly incomplete. An agent would not know how to construct the required headerMenus object or what windowId means in this context.

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 description provides a type hint (ISYS_HeaderMenus) for the first element of the args array, which adds a little meaning beyond the generic 'args' schema. However, it does not explain the structure or contents of that type, and the windowId parameter is not mentioned.

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 name and description clearly state a specific action: replacing header menus. The verb 'replace' distinguishes it from sibling operations like insert or remove, though the description does not explicitly contrast it with those alternatives.

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 about when to use this tool versus alternatives. The description only states the operation without any context, prerequisites, or exclusions.

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