list_directories

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

No annotations are supplied, so the description carries the full burden. 'List' implies a read-only operation, which is reasonable for this verb, but the description says nothing about privilege scoping (which directories are visible to the current user), whether results are paged, or what the return shape looks like. For a low-risk zero-parameter listing tool this is acceptable but not rich.

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?

A single tight sentence with the core purpose front-loaded and the 'filesystem paths' detail appended without waste. It is appropriately sized, though it stops just short of the detail that would make it fully self-sufficient.

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?

With no annotations and no output schema, the description is the only source of behavior, and it omits Oracle-relevant context such as visibility scoping (ALL_DIRECTORIES vs DBA_DIRECTORIES) and required privileges. Adequate for a trivial listing tool, but thin.

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 defines zero parameters, so there is nothing for the description to disambiguate; the baseline for a no-parameter tool is 4.

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?

States a specific verb (List) and resource (Oracle directory objects) and clarifies the output includes filesystem paths, which disambiguates it from OS-level directory listings. It is easily distinguished from siblings like list_schemas or list_datafile_io, though it does not explicitly name or exclude any sibling.

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?

There is no when-to-use guidance, no prerequisite or privilege context, and no mention of alternatives (e.g., run_query against ALL_DIRECTORIES/DBA_DIRECTORIES). The usage is only implied by the verb 'List'.

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