origin_drop_duplicates

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

No annotations provided, so description must carry burden. It discloses that the default behavior is in-place modification and how to write to a new sheet. However, it lacks details on irreversibility, permissions, or error handling. The description adequately covers the mutating aspect but could be more transparent.

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 three sentences: first states purpose, second explains subset, third explains keep and output options. It is front-loaded and free of unnecessary words, making it easy to scan.

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 covers the main functionality and key parameters, but leaves out source sheet parameters (book_name, sheet_name) and does not mention return value (though an output schema exists). For a data manipulation tool, it is moderately complete but has gaps.

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 description coverage is 0%, so description compensates partially. It explains subset (default all columns), keep options, and output_book/output_sheet usage. However, it does not describe book_name or sheet_name parameters (source sheet), and the exact format for subset (e.g., list of column names/indexes) is missing.

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 it removes duplicate worksheet rows. The purpose is specific and distinct from sibling tools like origin_filter_rows (which filters rows by criteria) or origin_melt_worksheet. However, it does not explicitly differentiate from all siblings, but the verb 'drop_duplicates' is self-explanatory.

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 explains parameter usage: subset limits columns, keep options (first/last/none), and output_book/output_sheet for new output instead of in-place. It does not provide explicit guidance on when to use this tool vs alternatives like origin_filter_rows for other filtering needs.

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