Find a Vinted brand

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

Annotations already declare readOnlyHint and openWorldHint. The description adds useful behavior beyond that: exact matching semantics (`exact: true`) and the fallback behavior for no matches, which is valuable context for the agent.

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 sentences, front-loaded with the purpose, and every clause adds value. No fluff or repetition of schema/annotation details.

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 lookup, it covers purpose, output shape, exact-match semantics, and no-match fallback. Without an output schema, return fields are only partially explained, but the description is sufficient for the tool's simplicity.

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 descriptions cover name and country, but the optional `limit` parameter has no description and the tool description doesn't explain it. The exact-match note relates to output rather than parameter semantics, leaving a moderate gap at ~67% schema coverage.

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 'Looks a brand up in Vinted's brand list and returns ranked candidates with their numeric id.' This uses a specific verb, identifies the resource, and describes the output, distinguishing it from siblings like find_category.

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 gives practical guidance: if nothing matches, the item can still be listed with brand unset, and explicitly says 'do not substitute a different brand.' It implies listing use but does not explicitly name alternative tools or when not to use this tool.

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