Get a Booli sold listing

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

The description declares the tool as 'Read-only,' consistent with the readOnlyHint annotation. It adds value by naming specific returned fields (final price, sold date) beyond the annotation. However, it omits error behaviors or authentication needs, which are acceptable given the simple retrieval nature and existing annotations.

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?

Description is two concise sentences: 'Full detail for one sold listing by its Booli id, including final price and sold date. Read-only.' No wasted words, front-loaded with purpose, and structured efficiently.

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?

Without an output schema, the description partially explains return values (final price, sold date) but leaves 'full detail' ambiguous. It does not cover possible errors or variations. For a simple retrieval tool, it is adequate but not comprehensive.

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?

Input schema has 100% description coverage with both parameters (booli_id, compact) documented. The tool description does not add additional parameter meaning beyond the schema, so the baseline score of 3 is appropriate.

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?

Description specifies 'Full detail for one sold listing by its Booli id, including final price and sold date.' It clearly identifies the action (get), resource (sold listing), and key outputs, distinguishing it from sibling tools like booli_get_listing which likely targets non-sold listings.

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 guidance on when to use this tool versus alternatives such as booli_search_sold or booli_get_listing. The purpose is implied by the name and description, but the description does not state when-not or provide context for selection among siblings.

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