vinted_member

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

No annotations exist, so the description carries the full burden. It thoroughly discloses included fields, deliberately excludes online-presence and activity data (last-seen timestamps, upload-frequency badges), and describes the data source as Vinted's server-rendered member page. This goes beyond basic read/write hints.

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?

Two concise sentences: first states the resource and return fields, second notes exclusions and data source. Every sentence adds value with no redundancy or filler.

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 one-parameter tool with no output schema, the description covers the return content, deliberate exclusions, and data provenance. It omits error handling or rate-limit behavior, which would add completeness but is not essential for a straightforward profile lookup.

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 input schema provides 100% coverage for the single parameter 'id' with a clear explanation ('Numeric Vinted member ID, from a /vinted/item result's seller link'). The description itself adds no additional parameter semantics, so baseline 3 applies.

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 'Returns a Vinted seller's public storefront profile' and enumerates the specific fields (username, location, rating, follower/following counts). This uses a specific verb+resource and distinguishes the member profile from sibling vinted_* item/brand/category tools.

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?

Implied usage is present: the id is sourced 'from a /vinted/item result's seller link', which suggests when to use it (follow-up on an item's seller). However, there is no explicit statement of when to use this versus alternatives or when not to use it.

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