My Vinted listings

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

Annotations already declare readOnlyHint=true, so the agent knows this is safe. The description adds that it returns listings with prices, views, and favourites, which is helpful context. However, it does not mention pagination behavior, status filtering, or any rate limits, which would be useful beyond the 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, front-loaded sentence that clearly states the purpose without any extraneous information. Every word contributes to understanding the tool's function.

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?

For a simple read-only list tool with annotations and schema, the description is mostly adequate, mentioning the key return fields. However, it does not mention pagination or the effect of status/country parameters, which could be important for an agent to know when calling the tool. No output schema exists, so more detail on the response shape would be beneficial.

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 50%: status and country have descriptions, while page and perPage do not. The description does not compensate for the missing parameter details, but the parameter names are fairly self-explanatory. It adds no additional meaning beyond the schema's existing descriptions.

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 lists the signed-in user's own listings, with specific fields (prices, views, favourites). This distinguishes it from sibling tools like search_items and get_item, which operate on the general marketplace or individual items.

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: it is for the signed-in user's own listings, which implies it should be used when the agent needs the current user's items. However, it does not explicitly name alternatives or exclusions, such as 'for other users' items, use search_items instead.'

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