NEXO Brain

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

With no annotations provided, the description carries full burden for behavioral disclosure. 'Delete an entity' implies a destructive, irreversible mutation, but it doesn't specify permissions required, confirmation prompts, side effects (e.g., cascading deletions), rate limits, or what happens on success/failure. This leaves critical behavioral traits undocumented for a destructive operation.

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 extremely concise at three words, with zero wasted text. It's front-loaded with the core action, though this brevity comes at the cost of completeness. Every word earns its place by stating the essential function, albeit minimally.

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 destructive nature, lack of annotations, 0% schema coverage, and presence of an output schema (which the description doesn't reference), the description is severely incomplete. It doesn't address safety, parameters, outcomes, or differentiation from siblings, making it inadequate for informed tool selection and invocation.

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 1 parameter with 0% description coverage, meaning the schema provides no documentation for the 'id' parameter. The description adds no parameter semantics—it doesn't explain what 'id' represents, its format constraints, or where to obtain valid IDs. For a tool with undocumented parameters, the description fails to 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 'Delete an entity' is a tautology that restates the tool name 'nexo_entity_delete'. It specifies the verb 'delete' and resource 'entity', but doesn't clarify what an 'entity' represents in this context or distinguish it from similar deletion tools like 'nexo_agent_delete' or 'nexo_credential_delete'. This provides minimal differentiation from siblings.

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. There's no mention of prerequisites (e.g., needing an existing entity), exclusions, or comparisons to sibling tools like 'nexo_entity_list' for verification or 'nexo_entity_update' for modification instead of deletion. The description offers zero contextual usage information.

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