parse_remove_from_array

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

The description mentions atomicity and primitive-only values, but lacks details on return values, error behavior, removal of all occurrences, or permissions. No annotations exist to fill the gap. The primitive-only claim conflicts with the schema, which allows object items and omits null, undermining transparency.

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 two concise sentences, front-loaded with the primary purpose and key constraint. No redundant information is present.

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?

As a mutation tool with no annotations, no output schema, and a nested parameter structure, the description is too sparse. It omits crucial behavioral details like removal semantics, return format, edge cases, and prerequisites, leaving significant gaps for an agent.

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?

The schema provides descriptions for nested properties (values, objectId, className, fieldName), but the top-level inputSchema parameter lacks description. The tool description adds context about primitive values, partially compensating for the 0% top-level 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?

The description clearly states the verb 'Elimina' (remove) and the resource 'un campo array' (an array field), specifying atomic removal of specific elements. This distinguishes it from siblings like parse_add_to_array and parse_remove_relation.

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 the tool is for removing primitive values from an array field, but provides no explicit when-to-use or when-not-to-use guidance. It does not mention alternatives or exclusions, leaving usage context to the reader.

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