add_text_before_text

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

With no annotations provided, the description carries the full burden. It discloses the return value (True on success) and the per-cell application, but does not mention side effects, permissions, reversibility, or whether the operation modifies the file in-place. This is a gap for a mutation tool.

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 clearly state the operation and return value, with no filler or repetition. Every sentence earns its place.

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 the tool's moderate complexity, absence of annotations, and 0% schema coverage, the description is incomplete. It does not cover parameter semantics, operational context, or edge cases. The existence of an output schema for the boolean return helps, but the description still leaves significant gaps for an agent to invoke correctly.

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 the description must explain parameters. It explains 'text' and 'select_text' but leaves '_range', 'worksheet', and 'file_token' undefined. The description uses vague 'worksheet range' without mapping to the actual parameters, which is insufficient for a 5-parameter tool.

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 adds specified text immediately before a target delimiter/selector text within worksheet cells, using a specific API. This specific verb+resource+scope distinguishes it from siblings like add_text_after_text, add_text_at_head, and remove_before_text.

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 implies usage for inserting text before a delimiter but does not explicitly state when to use this over alternatives or provide exclusions. It gives context by mentioning the target selector and worksheet range, but lacks explicit guidance on when not to use it.

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