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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful context that this is a navigational shelf of links that must be followed via sibling tools rather than a data payload in itself. It says nothing about auth, rate limits, or freshness of the curated set, so it adds modest value over the annotations.

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?

A single em-dash-delimited sentence that front-loads the resource name and then the content breakdown, followed by the routing hint. It is dense but every clause carries information; only the trailing routing clause could arguably live elsewhere.

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?

An output schema exists, so return values need not be explained. For a zero-parameter, read-only browse tool, the description conveys what the shelf contains and how to act on it, which is sufficient. Minor gaps around freshness/scope of the curation keep it short of 5.

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, so there is nothing for the description to disambiguate. Baseline 4 applies; no schema gap to compensate for.

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 resource ('GOAT curated links: the shelf GOAT is currently promoting') and enumerates the content types (seasonal collections, featured product searches, browse entry points). It clearly distinguishes itself from goat_collection/goat_search by presenting itself as the entry point that feeds them. It lacks a crisp verb, reading more as a noun phrase than an action statement, but the resource is unambiguous.

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?

It implies usage by stating each link is 'actionable via goat_collection or goat_search', which routes the agent to the right follow-up tools. However, it never states when to call goat_curated itself versus starting directly with goat_search, nor any exclusions. Usage is inferable but not explicit.

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