Search watched-tag galleries

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds useful context by explicitly stating it 'never changes watched tags or account settings,' reinforcing the read-only nature in domain-specific terms.

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 sentences with no wasted words. The primary action and resource are front-loaded, and the safety reassurance is kept brief and relevant.

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?

With a rich input schema, output schema, and strong annotations, the description is mostly complete for a read-only feed search tool. It could be stronger by explicitly naming sibling alternatives or saying when not to use it, but overall it provides sufficient high-level context for an agent to select and invoke the tool.

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 14 parameters in detail. The description adds a high-level grouping ('native search, category, advanced-filter, and cursor controls') but does not need to explain individual parameters because the schema handles that burden.

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 and resource: 'Read the authenticated user's watched-tag gallery feed' with search, category, advanced-filter, and cursor controls. This clearly distinguishes it from sibling tools like eh_search_galleries and eh_search_favorites by naming the watched-tag feed as the target.

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 implies usage context: use this tool to read and filter the watched-tag gallery feed. However, it does not explicitly state when to choose this tool over alternatives such as eh_search_galleries or eh_search_favorites, nor does it mention exclusions.

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