Add Text Before Text

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

With no annotations, the description carries the burden; it discloses that the tool mutates cells and returns True on success. It does not state side effects such as in-place file modification, permission requirements, or failure behavior, though the core behavior is 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?

Two concise sentences present the action, scope, and return behavior with no filler. The key behavior is front-loaded before the return-value note.

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 mutating 5-parameter tool with no annotations and 0% schema parameter descriptions, the description omits required behavior around optional ranges/worksheets, file handling, and preconditions. The presence of an output schema reduces the need to describe return values, but the operative details are still incomplete.

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 explains text and select_text as 'specified text' and 'target delimiter/selector text'. Required file_uuid and optional _range/worksheet semantics are left to inference from parameter names, so the description does not compensate for the schema gap.

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?

States a precise operation: adding specified text immediately before a target delimiter/selector text in each text cell of a worksheet range. This clearly distinguishes it from sibling tools like add_text_after_text and add_text_at_head/tail.

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 operation is described clearly enough that an agent can infer when to use it, but the description gives no explicit when-to-use/when-not-to-use guidance and does not name alternatives such as add_text_after_text or remove_before_text. Usage context is implied rather than stated.

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