catalog_upload

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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false and openWorldHint=true, so the safety profile is covered structurally. The description adds nothing beyond those flags – no mention of accepted file types, size limits, overwrite behavior, or what the returned icon identifier looks like, for a non-idempotent write.

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?

Three lines say the same thing twice ('Upload an icon' / 'Create an icon.') plus a raw endpoint string. It is short but redundant rather than front-loaded with useful information; two of three lines do not earn their 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 non-idempotent upload mutation with a nested multipart body and no output schema, the description says nothing about accepted formats, size constraints, or how the uploaded icon is subsequently referenced. The annotations cover safety hints but the description leaves the operational details entirely to the schema.

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 100% and the single multipart 'file' param is documented in the schema, so the baseline of 3 applies. The description adds no format, encoding, or content-type guidance beyond what the schema already states.

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 names a specific verb and resource (upload/create an icon), which is slightly more informative than the tool name 'catalog_upload'. However, it does not distinguish this from catalog siblings like catalog_create_or_update or catalog_post, and the three lines restate the same thing without adding scope.

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 indication of when to use this tool versus alternatives, no prerequisites (e.g., required permissions, whether the icon must later be referenced by ID), and no exclusions. The agent is left to infer everything from the name and the endpoint path.

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