Car market pulse

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds genuinely new behavior: the analysis is the vendor's own Persian text, and movers are new cars ranked by price change since their last quote. That language/content detail materially affects how an agent presents results. It omits freshness/caching or rate-limit behavior for a 'today' snapshot.

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 short paragraphs, front-loaded with what the tool returns, followed by usage and follow-up routing. Every clause carries information; nothing is redundant with the title.

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?

There is no output schema, so the description must describe the return payload, and it does enumerate the components (score, trend, analysis, movers). The Persian-language note pre-empts a real downstream surprise. Minor gap: no indication of how markets are keyed or how many markets are returned.

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?

With a single parameter at 100% schema coverage the baseline is 3, and the description earns a step up by defining what a mover actually is (new cars with the largest change since last quote), which is semantics the schema does not convey. It does not discuss the minimum of 0 or what a zero value returns.

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 output shape: today's car market mood (score, trend, per-market analysis) plus biggest price movers. This is clearly distinguishable from sibling list/detail tools like ba_price_list or ba_ad. It stops short of differentiating itself from the closest sibling ba_market_stats, which an agent would likely confuse it with.

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?

Gives an explicit use case in the user's own words ("is the car market rising today?") and names the correct follow-up tools (ba_new_prices, ba_price_list). It does not say when NOT to use it or what ba_market_stats is for instead, so the alternative-selection guidance is partial.

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