Find in-stock bras in a specific size from the live BraFinder catalog, with price. Give a size like "34DD". Links go to the BraFinder product page for each bra.
| Name | Required | Description | Default |
|---|---|---|---|
| size | Yes | A bra size like "34DD" (the size to find in stock). | |
| limit | No | How many to return (default 6). |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided; description covers real-time catalog and result format (price, links) but lacks details on empty results, caching, or other behaviors.
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 with no wasted words: first states purpose and key features, second gives example and output description.
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?
Complete given simple schema and no output schema; covers input format and output content, though default limit is not mentioned (handled by schema).
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% with descriptions for both parameters; description adds usage example and context about result links, providing additional value.
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 states it finds in-stock bras by size with price, and differentiates from siblings (bra_brand_fit, bra_size_dataset, translate_bra_size) by focusing on inventory search.
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?
Provides clear input example ('Give a size like "34DD"') and mentions result links, but does not explicitly state when not to use or mention alternatives.
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.