run_craigslist_postings_seller

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses the cost model ('1 point per returned record'), which is real value, but says nothing about pagination behavior, result limits, or authentication, leaving gaps for a list-endpoint tool.

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 tight sentences with the resource and scope front-loaded and the billing note trailing. No filler; every clause 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?

With no output schema and no annotations, the description should say more about what a record contains and how to page through results. It covers the core purpose and cost but leaves return-shape and pagination to inference.

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 schema already documents posting, sort, category, max_items, and start_page. The description adds only the notion of the seed posting; it does not enrich the other parameters, so the baseline 3 holds.

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?

States a specific resource and scope: 'All postings published by the seller of a given Craigslist posting', and clarifies with a parenthetical about full inventory. An agent can tell this apart from run_craigslist_postings or run_craigslist_postings_search, though no sibling is named explicitly.

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 phrase 'of a given Craigslist posting' implies you must supply a posting ID/URL and want that seller's other listings, but there is no explicit when-to-use vs alternatives or any exclusion guidance relative to the sibling search/list tools.

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