origin_clear_worksheet

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

No annotations are provided, so the description must disclose behavioral traits. It only says 'clear worksheet data' without detailing that data is permanently deleted, whether it affects other worksheet properties (e.g., formatting, formulas), or if confirmation is required. The option to preserve headers is noted, but scope and consequences are unclear.

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 a single, front-loaded sentence that efficiently communicates the core action and an optional behavior. However, it may be too sparse given the lack of annotations.

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 data-destructive tool with zero annotations and an output schema (not explained), the description is incomplete. It fails to mention return value, success/failure indications, or the effect on other worksheet elements. The sibling context suggests many similar tools, but no comparative guidance is given.

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?

With 0% schema description coverage, the description must compensate for parameter meaning. It only explains the keep_columns parameter ('optionally preserving column headers'), neglecting book_name and sheet_name. The agent lacks context for those parameters.

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 action (clear worksheet data) and the resource (worksheet), with the specific option of preserving column headers. This distinguishes it from sibling tools like origin_delete_columns (which deletes columns entirely) and origin_write_worksheet (which writes data).

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 provides no guidance on when to use this tool versus alternatives (e.g., origin_delete_columns for removing columns, or origin_write_worksheet for overwriting data). It does not mention prerequisites or contraindications.

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