NEXO Brain

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

No annotations are provided, so the description carries full burden. It only states the basic function without disclosing behavioral traits like permissions needed, rate limits, pagination, what 'search' entails (e.g., partial matches, case sensitivity), or response format. This leaves critical gaps for an AI agent.

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, efficient sentence with no wasted words. It's front-loaded and appropriately sized for a simple tool, though brevity contributes to gaps in other dimensions.

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 moderate complexity (search function with 2 parameters), no annotations, and an output schema (which helps), the description is incomplete. It lacks behavioral context and parameter details, but the presence of an output schema mitigates some need to explain return values. It's minimally adequate but has clear gaps.

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?

Schema description coverage is 0%, so the description must compensate. It mentions 'by name, value, or type,' which hints at the 'query' and 'type' parameters but doesn't explain their semantics, formats, or interactions. For example, it's unclear if 'query' searches across all fields or specific ones. This adds minimal value beyond the bare schema.

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 'Search entities by name, value, or type' clearly states the action (search) and target (entities), but it's vague about what 'entities' are in this context and doesn't differentiate from sibling tools like nexo_entity_list or nexo_entity_update. It specifies search criteria (name, value, type) which adds some specificity.

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 provides no guidance on when to use this tool versus alternatives like nexo_entity_list or nexo_entity_search. It mentions search criteria but doesn't explain context, prerequisites, or exclusions for usage.

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