typst_delete_file

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

No annotations are provided, so the description carries the full burden. It conveys that this is destructive ('Delete') and names the mutation, but says nothing about whether deletion is permanent, what happens when the path does not exist, or whether it cascades to referencing assets.

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 front-loaded sentence with the verb and resource first, then the domain and mechanism. The trailing 'via DeleteFilesMutation' is low-value implementation detail but does not bloat the definition.

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 two-parameter, no-output-schema destructive tool, the description covers identity but not consequences, error behavior, or auth requirements. Adequate to identify the call, thin for calling it safely.

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 both projectId and filePath are already documented, including the useful detail that filePath accepts a path/name or a file ID. The description adds no parameter information beyond the schema, so baseline 3 applies.

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: delete a file or asset in a Typst project, and identifies the underlying DeleteFilesMutation. It is distinguishable from typst_delete_project (project-level) and from typst_rename_file/typst_write_file, though it doesn't explicitly say so.

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?

No guidance on when to use this versus typst_rename_file, typst_write_file, or typst_delete_project, and no prerequisites such as auth or membership. The agent must infer usage entirely from the name and schema.

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