How a bra brand runs versus standard sizing: does it run small (size up) or large (size down), in band and cup. Give a brand for its specific fit note, or omit to get the brands that most notably run small or large. Use for "does [brand] run small", "which bra brands run large".
| Name | Required | Description | Default |
|---|---|---|---|
| brand | No | A brand name (optional). |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description bears the full burden. It describes the tool's behavior (returns fit notes or notable brands) but does not disclose data sources, accuracy, or any side effects. The description is adequate but not highly detailed.
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 sentence followed by usage examples—no wasted words. It is front-loaded with the core purpose and immediately followed by practical guidance.
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 tool with one optional parameter and no output schema, the description is complete: it explains when to use with/without the brand and what to expect. It does not detail return format, but that is acceptable for such a straightforward tool.
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 describes the single optional 'brand' parameter as 'A brand name (optional).' The description adds context: providing a brand returns its specific fit note, omitting it returns brands that run small or large. This adds value beyond the schema.
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's purpose: to determine how a bra brand runs relative to standard sizing in band and cup. It distinguishes itself from siblings like 'bra_size_dataset' (general sizing data) and 'translate_bra_size' (size conversion).
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 explicit usage examples: 'Give a brand for its specific fit note, or omit to get the brands that most notably run small or large.' It covers both use cases but does not explicitly state when not to use or mention alternatives to sibling tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Tools are mostly distinct: bra_brand_fit gives fit notes, translate_bra_size gives exact conversions, find_bras finds products, bra_size_dataset provides raw data. However, bra_brand_fit and translate_bra_size both deal with cross-brand sizing, which could cause minor confusion.
Naming patterns are mixed: 'find_bras' and 'translate_bra_size' follow verb_noun, while 'bra_brand_fit' and 'bra_size_dataset' are noun phrases starting with 'bra'. Inconsistent but still clear.
4 tools is reasonable for a niche domain like bra sizing. Not overly thin, covers key operations without excess. Could add one more tool for user contributions, but current count is appropriate.
Covers core use cases: finding fit notes, translating sizes, searching bras, and accessing the dataset. Missing update/delete operations, but this is a read-only informative server, so gaps are minor.