eda_sys_font_manager_add_font

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

No annotations are provided, so the description carries the full behavioral disclosure burden. It only states the return value (boolean success). It does not disclose what happens when the font already exists, whether fonts are persisted, what side effects occur, what a valid fontName is, or failure conditions. For a mutation tool with zero annotation coverage, this is a significant gap.

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 compact with no filler — a signature line plus two short Chinese sentences for purpose and return value. Information is front-loaded. Some redundancy exists (the signature and the Chinese purpose line repeat each other), but nothing is wasted.

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, and only a generic args array in the schema, the description must compensate but does not. It omits what fontName should be, side effects of adding a font, error/duplicate behavior, and persistence semantics. An agent cannot confidently invoke this tool correctly based on the description alone.

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?

Schema coverage is 100% for the top-level args/windowId parameters, so the baseline is 3. The signature line adds marginal value by revealing that args[0] is a string fontName, but it does not explain what format fontName should take (path, family name, URL) or how windowId relates to this operation. The description adds only slightly beyond the 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 states a specific verb and resource ('添加字体到字体列表' — add font to font list) and includes the full signature with return type. It can be distinguished from sibling tools like eda_sys_font_manager_delete_font and eda_sys_font_manager_get_fonts_list, though it relies heavily on the tool name itself.

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?

There is no guidance about when to use this tool versus alternatives, no mention of the sibling font manager tools (delete_font, get_fonts_list), and no prerequisites stated. An agent gets no help choosing this over other font operations or knowing when it applies.

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