Browse section galleries

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

Annotations already establish that this is a read-only, open-world operation. The description adds useful context about the returned `image` field being a direct crop suitable for view_image, but does not mention pagination, ordering, or other behavioral details. With annotations covering the safety profile, this is a modest but real addition.

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 sentences, front-loaded with the core action and section options, followed by the key output detail. No wasted language.

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 read-only listing tool with no output schema, the description covers the browse purpose and the central `image` return field. However, it omits `limit` semantics and does not describe the rest of the result shape, leaving gaps for correct invocation and expectation setting.

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 0%, so the description must compensate. It lists the section categories, but those duplicate the enum, and it says nothing about the `limit` parameter, its default, or its range. Half the parameters remain unclarified beyond their raw schema definitions.

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 uses a specific verb ('List') and resource ('Godly's curated section galleries'), and enumerates the section categories. It clearly distinguishes this browsing tool from get/search tools by emphasizing curated galleries, though it does not explicitly contrast with siblings like search_inspiration or get_inspiration.

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?

Usage is implied: browse section galleries and pass the returned image to view_image. However, the description does not state when to use this tool versus search_inspiration, get_inspiration, or list_categories. No exclusions or prerequisites are given.

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