List galleries

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

With no annotations provided, the description explicitly discloses that the operation is read-only and doesn't consume credits, which is critical for an agent. It also defines galleries clearly, adding context about their purpose. This goes beyond the schema and 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?

The description is two concise sentences. It front-loads the main action and resource, then provides necessary context and safety info without waste.

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?

The tool is simple, has complete schema coverage for parameters, and the description explains purpose, scope, ordering, and resource context. It also discloses read-only/no-credit behavior. This is sufficient for agent decision-making without an output 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?

The input schema already provides full descriptions for both parameters (page and per_page), and the description adds no extra meaning about these parameters. Baseline of 3 is appropriate because schema coverage is 100%.

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 clearly states the verb 'List' and the resource 'galleries' with scope 'for the current project', and specifies the ordering by 'slug, name, items_count'. This distinguishes it from sibling tools like get_gallery, create_gallery, update_gallery, and delete_gallery.

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 provides clear context for when to use the tool (listing galleries for the current project) and describes the output order. However, it does not explicitly mention alternatives or exclusions, such as using get_gallery for a single gallery.

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