alterios_resolve_project_icon

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

No annotations provided, so description must carry full burden. It vaguely mentions three resolution methods but does not disclose order of operations, state changes (e.g., upload may be destructive), or conditions for each path. Key behavioral traits like whether dry_run prevents upload are absent.

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?

Single sentence is concise but at the expense of necessary detail. It front-loads the core action but lacks structure; no parameter explanations, no usage context. Every sentence should earn its place; here it's too sparse for the tool's complexity.

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 11 parameters, no annotations, and an output schema, the description is incomplete. It doesn't explain the three resolution methods, how parameters control behavior, or what the output contains. Sibling tools further demand more context to avoid confusion.

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%, yet description adds no parameter details beyond mentioning 'semantic icon'. With 11 parameters including dry_run, allow_upload, and recurse, the description fails to explain any of them, leaving the agent to infer from names alone.

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?

Description clearly states the verb 'Resolve' and the resource 'one semantic icon' to a specific output 'project-local iconId'. It mentions three methods (registry, file-manager scan, guarded upload), distinguishing it from siblings like alterios_list_project_icons which list icons, and alterios_ensure_project_icons which ensures existence.

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 on when to use this tool versus alternatives. With many sibling tools for icons (list, export, ensure), explicit when/when-not advice is missing. The description neither suggests preferred use cases nor mentions exclusions.

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