Get a Booli for-sale listing

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint. The description adds that the listing must be active and for-sale, and states 'Read-only', which aligns with annotations. No contradiction; description adds minor behavioral context beyond 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?

The description is a single sentence plus 'Read-only', extremely concise with no wasted words. It effectively conveys the tool's purpose and key constraints in minimal space.

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?

The description covers the essential inputs and purpose, but lacks details about the output structure (no output schema). However, given the rich annotations and sibling context, it provides sufficient completeness for an agent to correctly select and invoke the tool.

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 clear descriptions for both parameters. The description adds extra context for booli_id (format from URL or search result), which enhances understanding beyond schema alone. Compact parameter is well described in schema.

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 clearly states it retrieves full detail for one active for-sale listing by Booli id. It distinguishes from siblings like booli_get_sold (sold listings) and booli_search_listings (search), making the specific resource and action unambiguous.

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 description specifies input type (numeric id from URL or search result) and that it's for active for-sale listings. It implies when to use (single listing detail) but does not explicitly exclude sold listings or mention alternatives, though sibling names provide hints.

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