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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered structurally. The description adds one genuinely useful behavioral fact, "Returns only public listings," which tells the agent results are visibility-filtered. It says nothing about pagination behavior, ordering, or result shape, so it adds some but not rich context beyond the 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?

Two sentences, front-loaded with the trigger condition, and the required-parameter fact comes second. The filter list is largely redundant with the schema and could be trimmed, but it does help an agent scan capabilities at a glance.

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 17 parameters, an output schema, and full annotation coverage, much of the burden is carried elsewhere, so the short description is defensible. Still missing is how this differs concretely from search_public_listings and list_public_profile_lists, and any note on paging or default result sizing, which matters for a 17-parameter list 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 94%, so the schema already explains every filter, including subtleties like the broad "q" search and the cursor paging contract. The description's filter enumeration (listId, listTitle, cultivar, color, price, photos, hybridizer, parentage, year) restates the schema without adding semantics, and it omits cursor/limit entirely. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

States a specific verb (browse) and a scoped resource (one seller's public catalog or one public list), which lets an agent distinguish it from the broad sweep implied by sibling search_public_listings. It does not name that sibling explicitly, so the differentiation is inferred rather than stated.

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?

"Use this when a buyer asks to browse one seller's public catalog or one public list" gives a clear situational trigger and implicitly excludes cross-seller discovery. No explicit when-not or named alternative (e.g. search_public_listings, list_public_profile_lists) is provided, which keeps it short of a 5.

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