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

readOnlyHint=true already tells the agent this is a safe read. The description adds value by naming the returned fields (id, name, path) since there is no output schema, but it omits pagination behavior despite limit/offset parameters (default 25, max 500) and says nothing about ordering or rate limits.

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?

Two short, front-loaded sentences with no filler; the purpose leads and the implementation detail follows. The parenthetical field list is compact and informative rather than redundant.

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 read-only list tool with full schema coverage and no output schema, the description is nearly sufficient: it names the resource, the scope, the returned fields, and the endpoint, so an agent can call it correctly without inspecting the API. It stops short of documenting pagination defaults and filter semantics, which are the only remaining gaps.

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%, so all five parameters (projectId, branchId, directoryId, limit, offset) are already documented in the schema, making 3 the baseline. The description's '(id, name, path)' refers to response fields, not parameters, so it adds no parameter meaning beyond the 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?

States a specific verb and resource ('List directories (folders) in a project') and even names the returned fields (id, name, path) plus the backing endpoint. It is clearly distinguishable from write siblings like crowdin_add_string, though it does not explicitly contrast itself with the nearest list siblings such as crowdin_list_branches or crowdin_list_files.

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 says what the tool returns but gives no when-to-use guidance: it never states that branchId/directoryId can scope results, nor when to prefer this over listing files or branches. The API endpoint reference is context, not usage instruction.

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