paste

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

Description states 'Read-only, no side effects,' which aligns with readOnlyHint annotation. Adds context about default output format (JSON) and raw option. Does not discuss potential edge cases but sufficient given annotation coverage.

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?

Description is three concise sentences with no fluff. First sentence defines core function, second covers safety and output, third provides usage guidance. Well-structured and front-loaded.

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 8 parameters fully documented in schema, description covers purpose, usage guidelines, and safety. No output schema but return format is described. Could add error handling info but not necessary for core use.

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 covers all 8 parameters with descriptions (100% coverage). Description adds marginal value by summarizing default delimiter and output format but does not elaborate on parameter details. Baseline score of 3 is appropriate.

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 merges corresponding lines from multiple files side by side with configurable delimiter. It distinguishes from sibling tools like 'join' (key-based merging) and 'cat' (simple concatenation).

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?

Explicitly tells when to use ('combine columns from separate files into a table') and when not to (not for key-based joining, not for simple concatenation), with specific alternative tool names ('join', 'cat').

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