list_directories

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

With no annotations provided, the description carries the full burden. It only says 'get list', which implies a read operation, but it does not disclose pagination behavior, permissions, or any side effects. This is a minimal disclosure 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 a single, front-loaded sentence with no redundant words. The parenthetical adds valuable domain context without bloat. Every word earns its place.

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?

For a simple list tool with only optional parameters and no output schema, the description provides essential context (including the note about status sets) and the schema covers pagination. It lacks some behavioral details (e.g., whether it returns all directories regardless of user permissions), but the tool is straightforward enough that this is not a major gap.

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 100% for all three parameters (fields, offset, pageSize), so the baseline is 3. The description adds no parameter-specific details, but the schema fully describes each parameter, so no further compensation is needed.

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 identifies the operation as retrieving a list of Planfix directories, using a specific verb and resource. The parenthetical note about task status sets adds useful context and helps differentiate from sibling tools like list_directory_entries and list_custom_fields.

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 description implies the tool is for getting directories but does not explicitly state when to use it over alternatives like list_directory_entries. The note about status sets provides partial context, but no clear exclusions or alternative tool references are given.

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