parse_add_to_array

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

With no annotations, the description carries the full burden but offers only atomicity and unique behavior. It contradicts the schema by stating only primitives (including null) are accepted while the schema allows objects and excludes null. It also does not disclose error cases or effects on non-array fields.

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, straight-to-the-point sentence. It is concise and front-loaded, though the value-type statement could be more precise to avoid contradiction.

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?

The description is very brief relative to the tool's mutation nature. It lacks details about prerequisites, side effects, error conditions, and return behavior. The value-type mismatch with the schema further reduces completeness, making the tool harder to use safely.

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 top-level 'inputSchema' parameter has no description, and the tool description does not compensate. It adds the unique behavior and value restriction, but the value restriction is misleading and contradicted by the nested schema, which already provides more reliable field descriptions.

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 uses a specific verb ('Añade elementos a un campo array') and identifies the resource (an array field), clearly distinguishing it from sibling tools like parse_remove_from_array and parse_add_relation. It also explains the unique option, which is relevant to the operation.

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?

No guidance is provided on when to use this tool versus alternatives such as parse_add_relation or parse_update_object. The description focuses on mechanism but does not mention prerequisites, scenarios, or exclusions.

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