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 mentions 'grouped by type' which adds some behavioral context about output organization, but doesn't disclose critical traits like whether this is a read-only operation, potential performance impact for large datasets, authentication requirements, or rate limits. For a list operation with no annotation coverage, this is insufficient.

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 that states the core functionality without unnecessary words. It's appropriately sized for a simple list operation and front-loads the key information.

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 has an output schema (which handles return values) and only one simple parameter, the description is reasonably complete for basic understanding. However, for a tool with no annotations and multiple sibling alternatives, it lacks sufficient context about behavioral characteristics and differentiation from similar tools.

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 description mentions 'grouped by type' which relates to the 'type' parameter in the schema, but with 0% schema description coverage, it doesn't explain what the 'type' parameter does (e.g., whether it filters to specific entity types or controls grouping). The description adds minimal value beyond the parameter name itself. With only one parameter and output schema available, baseline 3 is appropriate.

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 states the tool 'List all entities grouped by type', which clearly indicates a listing/read operation with grouping functionality. However, it doesn't specify what 'entities' are in this context or differentiate from sibling tools like 'nexo_entity_search' or 'nexo_entity_create'. The purpose is clear but lacks specificity about the resource domain.

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 about when to use this tool versus alternatives. With siblings like 'nexo_entity_search' (which likely filters entities) and 'nexo_entity_list' (which lists all), the description offers no comparison or context for selection. The agent must infer usage from the name alone.

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