Ad details

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

Annotations already cover read-only, idempotent, open-world behavior, and the description adds genuinely new context beyond them: phone numbers are masked by Bama and unavailable, and it explains what the related/similar counts actually represent on the ad page. No mention of what happens when the code is invalid or the ad is delisted, which keeps it short of a 5.

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?

Front-loaded with the core action and return contents, followed by when-to-use, then caveats — a sensible order with little filler. The middle sentence about ads_of_same_model/similar_total is dense and slightly opaque, referencing labels the agent may not otherwise recognize, which costs a point.

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, the description correctly takes on the burden of describing returned fields (price, specs, condition, seller, description, photos) plus the masking limitation and the meaning of related-ad counts. Combined with a fully documented three-parameter schema, an agent has everything needed to call and interpret it.

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 coverage is 100%, with the code format, kind enum/fallback and similar cap all documented in-schema, so the baseline applies. The description adds only a thin layer of meaning ('similar adds comparable car ads' vs. the wider similar pool), and the sentences about ads_of_same_model/ads_of_same_trim describe returned data rather than the three input parameters.

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 verb and resource ('Get one Bama ad') and enumerates the returned content (price, specs, condition, seller, description, photos). It also scopes the tool to ad types (car, motorcycle, truck), making it clearly distinguishable from the ba_search / ba_search_bikes_trucks siblings.

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?

Explicitly prescribes the workflow: 'Use it after ba_search or ba_search_bikes_trucks for a promising ad,' which tells the agent it is a detail fetch, not a discovery tool. It does not state when not to use it (e.g., batching many ads), but the sequencing guidance is clear.

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