Search Fabrics

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, covering safety and idempotency. The description adds valuable behavioral context beyond annotations: it specifies pagination (max 50 per page, returns has_more), error handling (empty data array if no matches), constraints (returns summaries only), and usage limits (do not call more than 3 times for same question). This enriches the agent's understanding without contradicting 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?

The description is well-structured with clear sections (USE WHEN, Filters, WORKFLOW, RETURNS, ERRORS, FALLBACK, CONSTRAINT, Chinese translation). It is appropriately sized for a search tool with many parameters and behavioral nuances. Some redundancy exists (e.g., 'Returns paginated fabric list' and RETURNS section), but overall, sentences earn their place by providing essential guidance and context.

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 the tool's complexity (8 parameters, search functionality) and rich annotations (readOnly, non-destructive, idempotent), the description is highly complete. It covers purpose, usage guidelines, behavioral traits (pagination, errors, constraints), and workflow integration with siblings. Although there is no output schema, the RETURNS section details the response structure, and the description compensates with comprehensive contextual information, making it fully adequate for agent use.

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 fully documents all 8 parameters. The description lists filters (category, weight range, composition, etc.) but does not add syntax, format, or semantic details beyond what the schema provides. For example, it mentions 'category (woven/knit/nonwoven/leather/functional)' which mirrors the schema's description. Baseline 3 is appropriate as the schema handles parameter documentation effectively.

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 states the tool's purpose: 'Search the Chinese fabric and textile database with lab-tested specifications.' It specifies the verb ('search'), resource ('Chinese fabric and textile database'), and scope ('lab-tested specifications'), distinguishing it from siblings like get_fabric_detail (full lab-test data) or get_fabric_suppliers (supplier information). The Chinese translation reinforces this clarity.

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 provides explicit usage guidance with 'USE WHEN' examples (e.g., user queries for specific fabrics or price ranges) and 'WORKFLOW' instructions (use as entry point, then call get_fabric_detail or get_fabric_suppliers). It also names alternatives (get_fabric_detail for full lab-test results) and includes fallback strategies (e.g., removing filters, limiting calls). This comprehensive guidance helps the agent select this tool appropriately.

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