lookup_products

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

No annotations provided, so description carries full burden. It does not disclose authentication, rate limits, or error handling. It mentions server behavior (sending name:value) but lacks deeper behavioral traits. Output schema may cover return values, but overall transparency is moderate.

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?

Well-structured with bullet points and clear separation of usage and parameter details. Slightly verbose but each sentence adds value. Could be trimmed slightly but maintains clarity.

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 3 parameters, no annotations, and presence of output schema, description covers usage workflow and parameter constraints comprehensively. Does not discuss output format but output schema likely handles that. Adequately 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?

Schema description coverage is 0%, but description compensates well. Explains query parameter format ('name:<product_name>' or plain name), and clarifies page/size defaults and bounds. Adds meaning beyond 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?

Description clearly states 'Look up products by name.' It provides a specific verb and resource, and distinguishes from sibling tools like search_leads by indicating it's a precursor to filtering leads by product.

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?

Explicitly states when to use: 'Use this BEFORE filtering leads by product when the user gives a product name.' Provides clear guidance on handling single vs multiple results and how to proceed with search_leads calls.

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