inspect_signal_file

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

While annotations are absent, the description clarifies the tool does not fully load the file and returns metadata. It implies read-only behavior but could be more explicit about side effects (none).

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 two sentences and a bullet list, front-loading the purpose and using no redundant 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?

Given the tool has one parameter, 100% schema coverage, and an output schema exists, the description adequately explains purpose, usage, and return values. It is complete for a simple inspection tool.

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 already covers the 'file_path' parameter with 100% description coverage. The tool description adds the file formats (CSV, WAV, NPY) but does not provide additional constraints or examples.

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 inspects a signal file without full loading and returns specific metadata. It distinguishes itself from the sibling 'load_signal_from_file' by explicitly recommending use before loading.

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 explicitly advises using this tool before 'load_signal_from_file' to verify format and plan loading parameters, giving clear when-to-use guidance.

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