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

No annotations are provided, so the description carries the full burden. It discloses that it lists templates and includes an optional query filter, but doesn't mention pagination, sorting, or the shape of the response. Since it's a read-only list operation, the safety profile is implied but not stated. The description adds the 'tailored AI agent template' context but lacks behavioral details like limits or ordering.

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 main purpose and examples, then the optional query. Zero fluff. Every word earns its place.

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 is a simple list with one optional param and no output schema, the description is mostly complete. However, it lacks any mention of response format (e.g., array of strings) or whether the query is case-insensitive. For an agent to use it effectively, these are minor gaps but with a single-param tool, this is near adequate.

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 single 'query' parameter is already documented in the schema. The description repeats the filter intent without adding new syntax or semantics. Baseline 3 is appropriate when schema covers the parameter fully.

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 verb 'List' and the resource 'industry verticals' with concrete examples (auto dealerships, trucking/dispatch, dental, HVAC) that distinguish it from sibling tools like get_pricing or book_demo. The scope is precise: it lists templates Lead Friendly ships for tailored AI agents.

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 read-only browsing use case but doesn't explicitly state when to use it versus alternatives. However, the sibling set (book_demo, check_capability, create_lead, get_pricing) is clearly different, and the tool's purpose is self-evident for discovery tasks. No exclusions or alternate routing provided, but context makes it clear enough.

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