search_products

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

No annotations are provided, so the description must disclose behavioral traits. It mentions 'Supports pagination' and 'Requires authentication,' which add useful context about response pagination and access prerequisites. However, it doesn't describe return format, ordering, or read-only status beyond what the name implies.

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 brief sentences that front-load the core function ('Search for products') and add only essential modifiers ('by name or keyword,' 'across the Milkbasket catalog,' 'Supports pagination,' 'Requires authentication'). No fluff or redundancy.

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 no output schema, the description provides enough context for a simple search tool: it states the purpose, pagination support, and auth requirement. It doesn't explicitly describe the response structure, but 'search for products' implies a product list, and the schema fully documents all parameters, making the description reasonably complete for this low-complexity 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?

The input schema covers all three parameters with descriptions (searchText, page, limit), achieving 100% schema coverage. The description adds no additional parameter-level detail beyond what the schema already provides, so the baseline of 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 clearly states 'Search for products by name or keyword across the Milkbasket catalog' – a specific verb and resource. It distinguishes from siblings like list_products by emphasizing keyword-based search, making it clear this is a search-tool rather than a list-all-tool.

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 for finding products by name/keyword but does not explicitly compare to alternatives such as list_products. No exclusions or 'when to use' guidance is provided, so usage is inferred rather than explicitly stated.

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