NEXO Brain

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It mentions 'clean up its entries' which hints at data deletion, but doesn't specify if this is reversible, what permissions are required, or potential side effects. No rate limits, error conditions, or output format are described.

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?

Extremely concise with two sentences that directly address purpose and parameters. The 'Args:' section is appropriately structured. Every word earns its place with zero redundancy.

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 one parameter with 0% schema coverage and an output schema (which relieves description from explaining returns), the description is minimally adequate. However, as a potentially destructive operation with no annotations, it should provide more behavioral context about what 'clean up' entails and any safety considerations.

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%, but the description compensates well by explaining the single parameter ('path: Path to directory to remove'). This adds clear meaning beyond the bare schema, though it doesn't specify path format constraints or examples.

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 ('Remove a directory from FTS5 indexing and clean up its entries') and specifies the resource (directory). It distinguishes from siblings like 'nexo_index_add_dir' by indicating removal rather than addition, but doesn't explicitly contrast with other indexing or file management tools.

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 on when to use this tool versus alternatives is provided. The description doesn't mention prerequisites, when-not-to-use scenarios, or refer to sibling tools like 'nexo_index_dirs' for listing indexed directories or 'nexo_reindex' for broader reindexing operations.

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