get_icon_metadata

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

The description discloses that the tool provides suggestions for unknown icons, which is a behavioral trait beyond the basic return of metadata. It also specifies the categories of metadata returned (tags, aliases, SVG path). However, it does not mention error handling, permissions, or side effects, though the 'get' verb implies read-only behavior.

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 front-loads the core purpose and provides useful detail without redundancy. Every word adds value.

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 simple one-parameter tool with no output schema, the description gives a good overview of the return content and handles the unknown icon case. It is complete enough for an agent to know what to expect, though it could benefit from explicitly stating the behavior for non-existent icons.

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 input schema already thoroughly describes the single 'name' parameter with examples, giving 100% coverage. The description does not add any additional meaning about the parameter beyond what the schema provides, so it is at baseline.

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 uses a specific verb 'Get' with a clear resource 'Lucide icon metadata' and lists concrete metadata types (tags, aliases, local SVG path, suggestions for unknown icons). This distinguishes it from sibling tools like get_icon_svg, which retrieves SVG content, and search_icons, which searches icons.

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 implies usage for retrieving metadata of a specific icon but does not explicitly state when to use this over alternatives like search_icons or list_icons. There is no mention of exclusions or when to prefer sibling tools. Context must be inferred from the tool name and the description's focus on metadata.

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