any

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

No annotations are provided, so the description carries the full burden. It explains the boolean return and the property handling for simple vs. object arrays, but fails to explain how the condition is specified (e.g., equality, custom function) or edge cases like empty arrays. This is a significant behavioral gap.

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 sentences with no fluff, and the first sentence immediately states the core behavior. The second sentence provides essential parameter guidance, though it is slightly dense but still efficient.

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 complexity (condition checking, array handling, parameter mismatch), the description is incomplete. It lacks details on how conditions are specified, what happens with empty arrays, and the overall parameter structure, making it hard for an agent to invoke the tool correctly without additional information.

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 input schema has zero parameters, yet the description references a 'propertyName' parameter, creating an inconsistency. The description adds some semantics for that parameter, but it's incomplete—missing the condition parameter and the array parameter itself. With no schema to rely on, the description does not sufficiently compensate.

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's function: returns True if any array item matches a condition, otherwise False. It also distinguishes between simple types and objects for the propertyName parameter, which sets it apart from siblings like 'every'.

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 specific guidance on when to use 'this' vs a property name based on array item type. However, it lacks explicit comparison to alternatives like 'every' or 'filter', so it doesn't fully clarify when to prefer this tool over siblings.

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