deregister_directory

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

With no annotations, the description takes on the full burden. It discloses key behavioral details: synchronous removal count, background chunk purge, and error on unknown collection. However, it does not explicitly warn that default keep_data=false leads to data deletion, which is a notable safety gap. Still, it goes beyond a minimal description.

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 concise and well-structured: a clear one-line purpose, followed by key behavioral notes, then Args. Every sentence adds value with no redundancy. It is efficiently front-loaded and easy to parse.

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 there is an output schema, the description does not need to explain return values, but it still mentions the removed-file count and background purge for clarity. It covers error behavior and parameter usage. It lacks mention of prerequisites (e.g., collection must already be registered), but that is implied by the error behavior. Overall, it is sufficiently complete for a two-parameter tool.

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 schema provides only titles for the two parameters, so the description's Args section fully compensates. It explains 'collection' as the name to deregister and clarifies that 'keep_data' preserves indexed data when true, implying deletion when false. This adds meaningful semantics beyond the raw schema.

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 'Remove a directory registration' with a specific verb and resource, making it clear this tool deregisters a directory. It distinguishes itself from siblings like 'register_directory' and 'delete' by focusing on registration removal. The first line is direct and unambiguous.

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 purpose implies usage for deregistering directories, and it mentions error behavior for unknown collections, but it does not explicitly compare with alternatives such as 'delete' or 'register_directory'. No clear 'when to use' vs 'when not to use' guidance is provided beyond the basic verb.

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