NEXO Brain

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states this is a creation tool, implying it's a write operation, but lacks details on permissions, side effects (e.g., if duplicates are allowed), error handling, or response format. The description is minimal and doesn't compensate for the absence of annotations.

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 with the core action and resource, making it easy to scan. Every part of the sentence contributes essential information about what the tool does.

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 (a write operation with 4 parameters) and the presence of an output schema (which reduces the need to describe return values), the description is moderately complete. It covers the basic purpose but lacks details on usage, behavioral traits, and parameter semantics, making it adequate but with clear gaps for effective tool selection.

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%, meaning parameters are undocumented in the schema. The description only lists entity types (person, service, URL), which partially explains the 'type' parameter but doesn't clarify 'name', 'value', or 'notes'. It adds some meaning but insufficiently compensates for the low coverage, leaving most parameters ambiguous.

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 action ('Create') and resource ('entity'), specifying entity types as person, service, or URL. It distinguishes from sibling tools like nexo_entity_delete, nexo_entity_list, nexo_entity_search, and nexo_entity_update by focusing on creation. However, it doesn't fully differentiate from other creation tools like nexo_credential_create or nexo_followup_create, which prevents a perfect score.

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. It doesn't mention prerequisites, such as whether an entity must be unique or if there are constraints on types, nor does it refer to sibling tools like nexo_entity_list for checking existing entities. Usage is implied only by the verb 'Create'.

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