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

The description states the tool returns 'total cost estimate and time hours', but the input schema includes no parameters for alteration type or garment type, and no output schema is provided. There is no disclosure of what the tool actually does with the body measurements, creating a significant transparency gap. Without annotations, the description fails to inform the agent of the tool's true behavior.

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 short but inaccurate. Conciseness is not beneficial when it introduces misinformation. Every sentence is misleading.

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 schema mismatch and lack of output schema, the description is completely inadequate. It does not help the agent understand what the tool does with the provided parameters or what results to expect.

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%, but the description does not explain the actual parameters (measurement_bust, measurement_waist, etc.) and instead describes unrelated inputs. This adds confusion rather than meaning. The description actively misrepresents the parameters.

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 claims the tool estimates dress alteration cost and time by alteration type and garment type, but the input schema requires body measurements (bust, waist, hips) and target dress size, with no mention of alteration types or garment types. This mismatch makes the purpose unclear and misleading.

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 suggests using for tailoring or wedding-dress budgeting and references a sibling tool list_bundles, but it does not explain when to use this tool vs. other similar tools (e.g., calculate_bra_size, calculate_clothing_size_convert). The actual usage context is obscured by the schema mismatch.

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