listing.inspect_current

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

With no annotations, the description carries the burden of behavioral disclosure. It includes a critical precondition (page_type == LISTING) but does not mention what the extraction returns, whether it navigates or only reads the current page, or how it handles failures or missing prerequisites.

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 consists of two short, front-loaded sentences with no redundant information. Every word contributes to the core purpose and a key constraint.

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?

Given no annotations, no output schema, and 0% parameter description coverage, this description is minimal. It omits return value details and parameter behavior, which are necessary for reliable invocation. The basic action and precondition are clear, but the tool is under-specified for an agent.

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?

The schema description coverage is 0%, so the description should compensate by explaining the three parameters (browser_session_id, include_description, include_seller_summary). It does not, leaving the agent to infer meanings from parameter names alone. The description adds no semantic depth beyond the 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 the tool extracts one listing from the current page, using a specific verb and resource. The precondition 'Requires page_type == LISTING' distinguishes it from sibling tools like listing.enumerate_member_inventory and listing.crawl_member_inventory, which operate on multiple 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?

The description provides clear context by requiring page_type == LISTING, telling the agent when the tool is applicable. However, it does not explicitly mention alternatives or when not to use it, though the sibling tool names suggest other listing-related operations.

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