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

With no annotations, the description provides useful behavioral details such as the filter query string format with an example and a pointer to the taxonomy for filter discovery. However, it omits return shape, pagination defaults, and any side-effect or authorization context, leaving gaps.

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 three sentences, each earning its place: the first states the purpose, the second explains filter syntax, and the third directs to the taxonomy. It's front-loaded and has no redundant content.

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 has no output schema and no annotations, so the description should explain return values and pagination behavior. It provides filter format and taxonomy pointer, but lacks information about what the browse response contains and how Page numbering works, making it only partially complete.

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 schema already describes all three parameters, giving a baseline of 3. The description adds value by explaining the filters format with a concrete example and linking facets to the taxonomy, which enhances understanding of 'filters' and 'category' beyond the schema.

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 identifies a 'Browse' operation on '1stDibs Items' with category, page, and filters, which distinguishes it from item_details (details) and search_items (search). However, it doesn't explicitly name alternatives, so it falls just short of full differentiation.

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 a workflow by telling the agent to 'Read the taxonomy to discover facets and filters,' which points to the read_taxonomy sibling tool. But it lacks explicit guidance on when to use browse_items over search_items or item_details, and no when-not-to-use conditions.

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