catalog_download

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered. The description only adds the underlying endpoint path, which is already repeated in the annotation title, and says nothing about the returned payload (binary image, base64, or JSON metadata) or error behavior for an unknown id.

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 opening "Download an icon" is immediately restated by "Download an existing icon by its unique id," and the GET path duplicates the annotation title, so roughly half the text is redundant. It is short, but not every line earns its place.

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 one-parameter read tool with no output schema, the definition covers the call itself adequately. The real gap is that nothing tells the agent what a "download" yields, which is the one thing an agent cannot infer for an icon-fetch endpoint.

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% and the single `id` parameter is documented as a UUID path parameter, so the schema does the work. "By its unique id" in the description adds no format or constraint detail beyond what the schema already states; baseline 3 applies for a single well-documented param.

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?

States a specific verb and resource: "Download an existing icon by its unique id." That distinguishes it from catalog_upload and catalog_delete_icons_by_id. It stops short of naming an alternative explicitly, so it is clear but not sibling-routing.

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 when-to-use or when-not-to-use guidance and no mention of the neighbouring catalog tools for fetching or deleting icons. The only implied usage is the self-evident one of retrieving an icon when you have its id.

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