calculate_bra_size

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

No annotations exist, so the description must fully disclose behavior. It states inputs, output, and the system parameter, but omits traits like whether the operation is read-only, safety implications, or any prerequisites. For a calculation tool, such gaps are moderate but not critical.

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 consists of two concise sentences: the first clearly defines the tool's purpose and inputs/outputs, and the second directs to related tools. Every word adds value with no redundancy.

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 tool's simplicity (3 parameters, no nested objects, output schema present), the description adequately covers what the tool does, its required inputs, and what it returns. It also provides a pointer for related calculators, making it contextually complete.

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 has no descriptions (0% coverage), so the description compensates by clarifying that underbust_cm and bust_cm are measurements in cm and that the system parameter chooses between FR, US, or UK. This adds meaningful context beyond the raw schema fields.

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?

Description clearly states verb 'calculate', resource 'bra size', and specifies three measurement systems (FR, US, UK) and input units (cm). It also lists the output fields, leaving no ambiguity about the tool's function. While there is a sibling 'calculate_bra_size_convert', the description sufficiently distinguishes this tool as it calculates from raw measurements.

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 mentions 'See list_bundles for related "textile-mode" calculators' which hints at alternative tools but does not explicitly state when to use this tool over others or provide exclusion criteria. Usage context is implied but not fully guided.

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