calculate_wallpaper

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

No annotations are provided, and the description only states it returns roll count, lacking details on side effects, constraints, or other behavioral traits. It does not disclose any safety information (e.g., that it's read-only) beyond the basic result.

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 highly concise, consisting of two clear sentences. The first sentence directly states the action, and the second provides context and a reference, with no wasted words.

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 description adequately covers the tool's purpose and mentions a related tool (list_bundles). However, it omits the fact that the pattern repeat parameter is not in the schema, and does not clarify if other settings (e.g., doors, windows) are considered. Given the output schema exists, return values are not needed.

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 100% coverage with descriptions, so the baseline is 3. The description adds some context by listing inputs (including a missing 'pattern repeat' parameter), which adds minimal value but introduces an inaccuracy.

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 wallpaper rolls needed for a room with a pattern repeat factor, for renovation budgeting. However, it mentions 'pattern repeat' as an input, which is not present in the input schema, creating a minor inconsistency.

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 it for renovation budgets and refers to list_bundles for related calculators, providing some context. However, it does not explicitly state when to avoid using it or how it differs from sibling tools.

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