NEXO Brain

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

With no annotations provided, the description carries the full burden of behavioral disclosure but fails to do so. It does not mention permissions required, whether the deletion is permanent or reversible, side effects, or any rate limits. The description is too minimal to inform the agent about the tool's behavior beyond the basic action.

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 with just three words, 'Delete a preference,' which is front-loaded and wastes no space. However, this conciseness comes at the cost of completeness, but as a standalone measure, it is maximally 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 (a deletion operation), lack of annotations, and 0% schema description coverage, the description is completely inadequate. It does not compensate for missing details, and while an output schema exists, the description fails to provide necessary context for safe and correct usage, making it insufficient for the agent.

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 0% description coverage, and the tool description adds no information about the 'key' parameter. It does not explain what a preference key is, its format, or examples, leaving the parameter's meaning entirely undocumented and unclear to the agent.

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 a preference' restates the tool name (nexo_preference_delete) with minimal elaboration, making it tautological. It does not specify what a 'preference' is in this context or distinguish it from sibling tools like nexo_preference_get, nexo_preference_list, or nexo_preference_set, leaving the purpose vague beyond the basic verb.

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 such as nexo_preference_set for updates or nexo_preference_get for retrieval. The description lacks any context, prerequisites, or exclusions, offering no help in selecting this tool over others in the list.

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