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

Annotations already mark the tool as read-only, open-world, and non-destructive. The description adds useful behavioral context: it uses a public JSON API, requires no login/browser/proxies, and has a cost of $0.02/call. This goes beyond the annotations, though it doesn't cover rate limits or error handling.

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 core action and resource. Both sentences add value: the first explains function and source, the second covers constraints and cost. No fluff.

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 good annotations (readOnly, non-destructive) and high schema coverage, the description is largely complete. It explains the source, auth requirements, cost, and input format. However, with no output schema, it doesn't describe the return structure or pagination behavior, so it's not fully 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 100% for both parameters, so the description doesn't need to add much. The description mentions 'by region and category,' which aligns with the `items` parameter but doesn't add any detail beyond the schema's thorough format explanation. Baseline 3 applies.

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 ('Pull') and identifies the exact resource ('live classified ad listings ... from Chotot's own public JSON API by region and category'). It clearly differentiates from sibling scrapers by naming Chotot Vietnam and listing example categories.

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?

No explicit when-to-use or alternatives are provided; however, the description implies usage for Chotot Vietnam listings and highlights convenience ('No login, no browser, no proxies'). It doesn't mention exclusions or compare to other scraper tools, so it's only implied.

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