tenki_remove_path

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

Annotations already declare destructiveHint=true and readOnlyHint=false, and the description builds on this by specifying recursive removal of non-empty directory contents, matching rm -r behavior. It clarifies what gets destroyed without contradicting annotations, though it doesn't mention error cases or irreversibility beyond the existing destructive hint.

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, focused sentences: the first states the primary action, the second clarifies recursive behavior. No filler, no repetition of schema details, and the key information is front-loaded.

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 three-parameter delete tool with full schema coverage and destructive annotations, the description is sufficient. It covers the operation, sandbox scope, and recursive semantics; no output schema exists, so return values are not expected. It could mention behavior on missing paths, but that is not essential for correct invocation.

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 coverage is 100%, providing baseline 3. The description adds the 'non-empty directory' qualifier and the rm -r analogy, which clarifies when recursive is required beyond the schema's 'Remove a directory and its contents (default false)'.

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 states a specific verb 'Delete' and resource 'file or directory in a sandbox', distinguishing it from sibling tools like tenki_read_file, tenki_write_file, tenki_move_path. The 'rm -r' analogy further reinforces the deletion semantics.

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 usage as the deletion tool for sandbox filesystem paths but does not explicitly state when to use it versus alternatives such as tenki_move_path or executing rm via tenki_exec. It lacks when-not guidance or exclusion conditions, leaving usage inference to the agent.

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