listing.enumerate_member_inventory

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

With no annotations provided, the description carries full responsibility for disclosing behavioral traits. It mentions 'visible' tiles but does not explain side effects such as scrolling behavior, limits, or whether the page is mutated. The tool likely interacts with the browser (given the browser_session_id parameter), but this is unaddressed.

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 concise sentence with no filler or redundancy. It is appropriately front-loaded, though arguably too brief for the tool's complexity, making it more under-specified than structurally wasteful.

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 the tool has five parameters, no annotations, and no output schema, the description is far too sparse. It does not explain return values, scrolling behavior, metadata retrieval, or when to stop, leaving critical gaps for an agent to use the tool correctly.

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%, yet the description provides no explanation of any of the five parameters (max_listings, scroll_limit, include_tile_metadata, etc.). The description does not help an agent understand what each parameter controls or how they affect the enumeration.

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 uses a specific verb ('Enumerates') and identifies the resource ('visible listing tiles on a member profile page'), making the core purpose clear. It does not explicitly contrast with sibling tool 'listing.crawl_member_inventory' which likely performs a broader crawl, so it lacks full differentiation.

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 guidance is given on when to use this tool versus alternatives like 'listing.crawl_member_inventory'. The description simply states what it does, without explaining context, prerequisites, or exclusions.

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