remove_before_text

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

No annotations are provided, so the description must fully disclose behavior. It mentions 'Returns True if the operation succeeds' and 'within each text cell', but does not explain side effects, reversibility, what happens when the delimiter is absent, or how case sensitivity and range selection behave. This leaves significant behavioral gaps.

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 with no filler. It states the core operation, the scope, the API, and the return value efficiently, making every word purposeful.

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?

With 5 parameters, no annotations, and an output schema, the description is too sparse to be complete. It does not cover parameter semantics, default behavior, or edge cases, leaving an agent to guess at critical details like which parameters define the range and how case_sensitive affects the operation.

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%, and the description only clarifies that 'text' is the delimiter text. It does not explain file_token, _range, worksheet, or case_sensitive, all of which are essential for proper invocation. The description adds minimal meaning beyond the schema.

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 specifies the action: removing all characters before a delimiter text within text cells in a worksheet range, and the 'to the left of' clarification disambiguates from remove_after_text. It identifies the resource and operation precisely, distinguishing it from sibling tools.

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?

Usage is implied by the description: use this tool when you need to strip characters preceding a delimiter in worksheet text cells. However, it does not explicitly mention alternatives or exclusion criteria, such as when to use remove_after_text or trim_text, so guidance is only implicit.

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