interpolate

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

No annotations are present, so the description carries full burden. It discloses that a new output sheet is created and returns resampled X and Y, but does not mention if original data is preserved, auth needs, or handling of edge cases (e.g., missing data).

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 very short and front-loaded with the core action. It includes an args/returns section, which is helpful, but the lack of detail on required parameters prevents a perfect score.

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 is incomplete given the tool's complexity (6 parameters, output schema). It explains only the optional parameters and assumes the agent knows the format of 'data_book' and 'data_sheet'. No prerequisites or data format expectations are stated.

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 0%, and the description only explains 'num_points' and 'method' (2 of 6 parameters). Required parameters like 'data_book', 'data_sheet', 'x_col', 'y_col' get no explanation, forcing the agent to infer their meaning from names.

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 'Resample an XY curve onto evenly spaced X values' uses a specific verb and resource, clearly distinguishing this interpolation tool from similar siblings like 'smooth' or 'integrate'.

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?

No explicit when-to-use or when-not-to-use guidance is provided. While the purpose is clear, the description does not help the agent decide between this and related tools like 'curve_fit' or 'smooth'.

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