fgui_import_font

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

With no annotations, the description carries the full burden of behavioral disclosure. It does disclose that this is a disk write operation and mentions the conflict policy (reject, auto-rename, replace), which conveys that it may overwrite or rename existing files. However, it does not discuss side effects such as what happens to existing fonts, whether the operation is reversible, or any permission requirements. The transparency is partial but not misleading.

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, efficient sentence that front-loads the primary action and then adds the key caveat about disk writes and conflict handling. There is no redundancy or filler, making it appropriately concise and well structured.

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 has 8 parameters with zero schema description coverage and no annotations, the description is insufficient for an agent to call it correctly. It fails to explain most parameter semantics, does not mention any prerequisites (e.g., an open document or package), and lacks information about return behavior. The description is far from complete for the tool's complexity.

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 description coverage is 0%, so the description must compensate. It explains that source_path is an absolute local path and hints at conflict_policy via the rejection/rename/replace mention. However, it does not clarify the other six parameters (package_name, exported, folder_path, resource_name, create_folders, timeout_seconds), leaving the agent without sufficient understanding of their meaning or defaults.

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 action: importing a font from an absolute local path. It specifies the resource type (font) and the source location, distinguishing it from sibling import tools like import_image and import_sound. The verb 'import' and resource 'font' are explicit and unambiguous.

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 provides no explicit guidance on when to use this tool versus alternatives. It does not mention prerequisites, conditions, or exclusions. The only implied usage is that it is for fonts, which is already obvious from the name. There is no discussion of when a different import tool would be more appropriate.

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