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

No annotations are provided, so the description must convey behavioral traits. It states the tool considers hems and pattern repeat and returns fabric length to buy. This is clear for a non-destructive calculation tool, though it does not mention that it is read-only.

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 concise with three sentences, front-loading the purpose and key inputs. The reference to list_bundles is efficient, though it could be trimmed without loss.

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?

The tool has an output schema, reducing the need to describe return values. However, the description mentions pattern repeat which is not in the schema, creating a completeness gap. It provides adequate context for a simple calculator but could be more accurate.

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 all parameters, but the description mentions 'pattern repeat' as an input that is not present in the schema. This inconsistency could mislead the agent. The description adds no additional meaning beyond the schema and introduces confusion.

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 computes curtain fabric meters including hems and pattern repeat. It specifies inputs and output. It distinguishes from siblings by referencing 'textile-mode' calculators, but does not directly name similar tools like calculate_fabric_yardage.

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 says 'Use for sewing' providing a usage context, but it lacks explicit guidance on when not to use this tool versus other fabric calculators. Without exclusions or alternatives, the agent may not differentiate effectively.

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