isnullorempty

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

The description discloses the core behavior (null/empty check) and the supported types, but it does not define what 'empty' means for each type (e.g., empty string, empty array, empty object) or clarify the return value. With no annotations provided, the description carries the full burden for behavioral disclosure, and more detail would be beneficial.

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, clear sentence that directly states the tool's purpose and applicable types. There is no unnecessary information, making it appropriately concise and well-structured.

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?

For a simple predicate tool, the description covers the essential usage and type applicability. However, it lacks explicit definitions of 'empty' for each type and does not mention the return value. Since there are no annotations or output schema, a bit more detail would enhance completeness, but the low complexity makes this adequate.

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?

Since the schema has zero parameters, the baseline is 4. The description adds useful semantic context by indicating the implicit 'value' can be a string, array, or object, which helps the agent understand the expected input despite the lack of formal parameters.

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: checking if a value is null or empty. It specifies the applicable types (Strings, Arrays, Objects), which distinguishes it from sibling tools like isstring or isarray that focus solely on type checks.

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 mentions that the tool can be used for Strings, Arrays, or Objects, providing some context on applicable use cases. However, it does not explicitly state when to use this tool versus alternatives, nor does it mention any when-not-to-use conditions.

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