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

With no annotations, the description carries the full disclosure burden and largely fails: it does not say whether the call is read-only, whether scoring requires a live/active listing, how fresh the score is, or whether it can fail for expired listings. The only behavioral hint is the mention of a condition-adjusted tier, which implies an output shape but no operational behavior.

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?

One short sentence with no filler, front-loading the owner and the returned value. It is efficient, though the fragmentary phrasing trades clarity for brevity.

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?

For a tool with no annotations, no output schema, and an undocumented required parameter, the description should do more. It never defines what a 'condition-adjusted tier' is, what scale the score uses, or what the caller receives, leaving core calling context missing.

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 0% for the single required 'id' parameter, so the description must compensate. Saying 'for a live listing' implies the id is a listing identifier and that the listing should be live, which adds modest meaning, but it does not give the id format or confirm it is not a score id or user id.

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 identifies the resource it concerns (a live listing) and the value it produces (BidProwl's deal score plus a condition-adjusted tier), so an agent knows the general subject. However, it is phrased as a noun fragment without a verb, leaving unclear whether it fetches, computes, or caches the score, and it does not distinguish itself from siblings like get_listing or sold_comps.

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?

There is no statement of when to use this tool versus get_listing, sold_comps, or search_listings. A reader can guess it is used when a deal score is wanted, but no condition, prerequisite, or alternative is given.

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