alterios_export_project_icons

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

No annotations are provided, so the description must fully disclose behavioral traits. It mentions exporting to local artifacts but lacks details on side effects (e.g., file creation), required permissions, error conditions, or whether the operation is destructive. The description is too brief to be transparent.

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 concise sentence that is easy to parse. However, it could be restructured to add more value without increasing length significantly. It is appropriately front-loaded but lacks depth.

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 7 parameters, no parameter descriptions, no annotations, and an output schema (not shown), the description is insufficient. It does not explain what 'local artifacts' means, how the usage guide is generated, or how to specify the source folder. The tool requires more context to be usable.

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%, and the description provides no explanation of the 7 parameters (profile, recurse, max_files, project_id, folder_hash, download_files, icons_folder_name). The tool name and one-line description leave the purpose of each parameter completely ambiguous.

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 (export), resource (icons from an Alterios elFinder folder), and outcome (to local artifacts with a generated usage guide). It distinguishes from sibling tools like alterios_list_project_icons and alterios_resolve_project_icon.

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 such as alterios_list_project_icons or alterios_resolve_project_icon. No context about prerequisites or use cases is given.

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