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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds the endpoint URL and the returned identifier fields, but says nothing about pagination, result size, or rate limits. With annotations carrying the safety burden, this is adequate but not rich.

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?

Two tight sentences with the core action and scope front-loaded, followed by the practical 'start here' guidance and the raw endpoint. Nothing is redundant, though the endpoint URL is marginal value for an agent choosing a tool.

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 zero-parameter read tool with no output schema, the description covers what it returns (catalogUid, title) and when to use it. The main omission is the shape/size of the result set and whether pagination applies.

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 tool takes zero parameters, which is the baseline-4 case since there is nothing for the description to disambiguate. The mention of catalogUid and title describes outputs rather than inputs, so no additional parameter meaning is needed or missing.

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?

Names a specific verb and resource ('List Gelato's product catalogs'), illustrates the scope with concrete catalog types (posters, cards, t-shirts, mugs, photo books), and states the identifying fields returned (catalogUid, title). It does not explicitly contrast itself with the singular sibling gelato_get_catalog, relying on the list/get naming distinction instead.

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?

'Start here to find products' gives a clear entry-point cue for when to reach for this tool. It stops short of naming alternatives or exclusions, so an agent must infer that gelato_get_catalog or gelato_search_products handle narrower lookups.

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