ck_fs_ls

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

Discloses read-only behavior ('no files are modified'). Describes path parameter usage. No annotations provided, so description fully carries transparency burden.

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?

Four sentences, front-loaded with main function, no redundancy. Every sentence adds value.

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?

Fully covers what the tool does, how to use it, and when to choose alternatives. No output schema needed for a listing command.

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?

Although schema coverage is 67%, the description adds meaning for the undocumented 'path' parameter by stating it is a relative path and default behavior. Other parameters have schema descriptions.

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?

Description clearly states 'List files and directories inside the bound project root' with specific verb and resource. It distinguishes from sibling tools by mentioning ck_fs_find, ck_fs_read, ck_fs_grep.

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?

Explicitly says when to use this tool ('to browse directory structure') and when to use alternatives ('Use ck_fs_find to locate files...'). Also notes read-only nature.

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