goat_collection

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does well by stating this is 'Credential-free public data' (no auth needed), that it returns a 'page' of results (pagination behavior), and that slugs are not enumerable (a key behavioral limitation). It doesn't describe the exact response shape or error behavior, but for a read-only public data endpoint, the key behavioral traits are covered.

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 compact and information-dense. Every sentence earns its place: the first defines the resource, the second explains the use case and provenance, the third gives a critical constraint, and the fourth states the auth requirement. The most important operational detail (slug not enumerable) is front-loaded in the middle where it's hard to miss.

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 paginated read endpoint with 4 well-documented parameters and no output schema, the description covers the essential context: what the resource is, how to obtain the required slug, and that no credentials are needed. It doesn't describe the response format, but since there's no output schema and the tool is a simple collection fetch, the description is nearly complete. The only minor gap is not stating what the response items look like (e.g., product objects with ids, names, prices).

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%, so the schema already documents all four parameters (slug, page, limit, exclude_product_ids). The description adds context for the slug parameter by explaining it must be captured from a live GOAT page, which is genuinely useful beyond the schema. However, it doesn't add meaning for page, limit, or exclude_product_ids beyond what the schema already provides. Baseline 3 is appropriate given full schema coverage.

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 states a specific verb ('Get'), a clear resource ('a GOAT curated product collection'), and explains what that means with concrete examples ('top trending', 'new arrivals'). It also distinguishes this from other GOAT tools by noting it's the same call used for 'you may also like' rails and homepage modules, which helps an agent understand exactly what this tool returns.

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 explicitly tells the agent when to use this tool (to fetch a curated collection/editorial rail) and provides a critical usage constraint: 'Collection slugs are not enumerable by this API -- capture one from a live GOAT page.' This is actionable guidance that prevents an agent from trying to discover slugs through this tool. It also implicitly distinguishes it from search tools like goat_search and goat_curated by describing the specific editorial-rail use case.

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