My shop at a glance

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

Annotations only provide readOnlyHint and openWorldHint. The description adds valuable behavior: stats are computed from listing pages, and the `note` field discloses how much of the shop was actually read. This transparency about the computation method and potential incompleteness goes 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 two sentences with no wasted words. It front-loads the core purpose, then efficiently explains the computational method and the caveat about the note field. Every sentence earns its place.

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 lack of an output schema, the description adequately enumerates the main returned metrics (active/sold counts, total active value, views, favourites) and mentions the note field for coverage. It also explains the data source and the absence of a native endpoint, providing enough context for an agent to understand the tool's behavior.

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% for both parameters, setting a baseline of 3. The description enhances the meaning of the 'pages' parameter by linking it to the `note` field, explaining that how many pages read directly affects the coverage of the shop stats. This adds context not present in the schema alone.

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 'Aggregates' and clearly identifies the resource as 'the signed-in seller's shop', listing concrete metrics (active/sold counts, total active value, views, favourites). This distinguishes it from sibling tools like my_listings or whoami, which serve different purposes.

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 implies usage by stating that Vinted has no stats endpoint, so this tool is the means to obtain shop statistics. However, it does not explicitly state when to prefer this over alternatives or when not to use it. No direct comparison or exclusion criteria are provided.

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