mne_crop

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

The description discloses that the operation is performed 'in place,' which is a key behavioral trait. However, it does not mention return values, side effects on the object, error conditions, or the meaning of default values.

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 entire description is a single, focused sentence without redundant information.

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?

For a simple tool, the description covers the core action and important in-place behavior. However, it lacks alternatives context and parameter details, making it somewhat incomplete.

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 description defines the time window [tmin, tmax] in seconds, which clarifies the two time parameters. However, the 'name' parameter is unexplained, and the description does not compensate for the complete lack of schema-level parameter descriptions.

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 a specific action ('Crop') on specific resource types ('Raw/Epochs/Evoked object') with the time window scope, distinguishing it from siblings like filtering or resampling.

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 does not explicitly state when to use this tool versus alternatives, nor does it mention exclusions. The intended use is implied by the action, but no guidance is provided for selection.

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