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

With no annotations provided, the description carries the full behavioral burden. It communicates that the tool is a read operation ('Returns') and notes an availability limitation for automotive clients, but it does not disclose other behavioral traits such as authentication requirements, rate limits, response format, or whether results are live or cached.

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 two sentences, immediately front-loads the core functionality, and includes only meaningful details. No redundant or filler content exists; every sentence adds value.

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 low complexity (2 parameters, simple list operation) and the presence of a complete input schema, the description adequately covers purpose and scope. It omits return structure, but since there is no output schema, a brief mention of response format would be helpful; however, the description is still sufficient for a straightforward read-only list 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 already provides descriptions for both parameters (100% coverage). The description adds semantic detail by mapping the category enum values to specific offer types (e.g., 'new-vehicle APR/lease specials', 'service & parts coupons'), which clarifies what each category means beyond the schema's generic 'Filter by category.'

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 uses a specific verb 'Returns' and identifies the exact resource: the dealership's current specials and offers. It enumerates concrete categories (new-vehicle APR/lease, pre-owned, service & parts, rebates, incentive programs), which clearly distinguishes it from sibling tools like get_vehicle_details or get_reviews.

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 the use case: when you need to retrieve dealership specials or offers. It includes a notable constraint—'Only available for automotive clients'—but does not explicitly compare with alternative tools or provide when-not-to-use guidance. No sibling tools are referenced.

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