get_user_inventory

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

No annotations are provided, so the description must carry the full burden. The minimal phrase 'Returns the list of listings' does not disclose whether this is a read-only operation, whether it requires authentication, how pagination works (despite pagination parameters in the schema), or any rate limits. It fails to add behavioral context beyond what the schema trivially implies.

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 brief sentence, which is under-specified for a tool with six parameters and no schema descriptions. It is not appropriately sized; it lacks necessary context while being overly concise, reducing its practical value.

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 complexity (six parameters, three enums, no output schema, no annotations), the description is severely incomplete. It does not explain what 'inventory' means in this domain, how pagination functions, what statuses are available, or what the response contains. The description fails to provide sufficient context for correct tool invocation.

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%, meaning no parameter descriptions exist. The tool description adds no meaning to any of the six parameters (username, status, page, per_page, sort, sort_order). The agent is left to guess the semantics of enums like 'status' or 'sort' without explanation.

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 'Returns the list of listings in a user's inventory' clearly indicates the tool retrieves items from a user's marketplace inventory. It is distinct from sibling tools like get_marketplace_listing (single listing) or get_user_collection_items (collection, not inventory). However, it lacks specificity about scope and filtering options that would further clarify the purpose.

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 provided on when to use this tool or how it compares to alternatives. With many sibling tools for similar user data retrieval, the absence of usage context forces the agent to infer based solely on the tool name.

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