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

No annotations are provided, so the description carries full responsibility. It discloses read-only status, pagination behavior (nextOffset, hasMore), response fields, ordering by gallery order, and edge cases (empty array, not-found result). This is more than enough for an agent to understand what happens when invoking the tool.

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 longer than average but well-structured: read-only declaration, main return value, usage, sibling routing, tags, ordering, response fields, pagination, and edge cases. Each sentence serves a purpose, though a slight tightening of the pagination wording could improve it.

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 read-only list tool with four parameters, no output schema, and no annotations, the description provides comprehensive context: output shape, pagination controls, ordering, filter values, and failure/empty behavior. Nothing critical appears missing for an agent to invoke it correctly.

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 coverage is 100%, so the baseline is 3. The description adds meaningful value on top of the schema: it enumerates known tag values, gives an example project slug ('le-requin'), explains offset semantics in terms of nextOffset from a previous response, and clarifies behavior for unmatched or invalid project filters.

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 begins with 'Read-only. Returns a paginated list of gallery photo summaries' – a specific verb and resource, followed by the exact fields returned (captions, URLs, references, tags, metadata). It also explicitly contrasts itself with get_build_details, so an agent can identify unique purpose without ambiguity.

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 states directly when to use this tool ('browse gallery photos or filter them by model project and gallery section') and when to use a sibling instead ('Use get_build_details when the user needs vessel background, technical notes, or build-log content'). It also provides known section tags that act as filter guidance.

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