Browse galleries by tag

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

With readOnlyHint and openWorldHint already in annotations, the safety profile is covered. The description adds the scoping constraint (one tag, one source) but does not disclose any additional behavioral traits such as rate limits, pagination behavior, or result ordering. That is adequate but not rich.

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 short sentences with no filler. The core behavior is front-loaded, and the routing guidance is separated onto a second line that earns its place.

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?

Given a fully documented input schema, an output schema, and annotations, the description is nearly complete. It covers what the tool does and when to prefer it. The only small gap is not explicitly contrasting it with the browse sibling, but 'one tag on one source' already implies that distinction.

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 input schema already documents every parameter. The description adds only a slight hint that 'tag' can come from get_gallery, but it does not clarify formats, defaults, or enum semantics beyond what the schema provides. The baseline 3 is appropriate.

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 opens with a specific verb and resource: 'List galleries for one tag on one source.' It states the exact scope of the operation and explicitly routes around search(), distinguishing this tool from one of its key siblings. This gives an agent a clear basis for selecting it.

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 second sentence gives explicit guidance: 'Prefer this over search() when you already have a tag from get_gallery.' This is a concrete when-to-use rule with an alternative named. It does not explicitly mention when not to use browse, but the context-for-use is otherwise clear.

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