remove_from_array

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

Covers the core behavior: removes first matching element, works for multiple file types, uses stripped equality. Lacks explicit mention that it modifies the file. No annotations to contradict.

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?

Well-structured with clear paragraphs, usage guidelines, and examples. Slightly verbose but efficient for the complexity covered.

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?

Provides enough detail for a complex tool, missing only explicit file_path explanation and side-effects. Output schema exists to cover return values, reducing burden.

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?

Explains target and value_match well, including examples. But file_path is not described anywhere in the description, leaving a gap for 0% schema coverage.

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?

Explicitly states it removes the first element matching value_match from an array/list. Distinguishes from sibling delete_key (removes whole key) and append_to_array. Specifies stripped text equality.

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?

Provides explicit 'Use this when' and 'Don't use this when' guidance, naming the alternative tool (delete_key). Clearly defines the context of use.

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