delete_project_file

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

With no annotations, the description must cover behavioral traits. It only states the action without mentioning destructiveness, permissions, or side effects. The 'operation_type' parameter hints at non-deletion functions (adjust position, unlock all), creating ambiguity.

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 short sentence, efficiently conveying core purpose. It is front-loaded but lacks details that would improve usability without excess.

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?

Given three parameters, no output schema, and no annotations, the description does not fully explain the tool's behavior. The operation_type parameter's dual purpose is not addressed, leaving the agent uncertain.

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?

Though schema coverage is 100%, the description adds no meaning beyond parameter names. The 'operation_type' parameter's enum values (adjust first sentence position, unlock all) are unexplained and seem unrelated to deletion, causing confusion.

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 states the verb (delete) and resource (project file). It distinguishes from siblings like 'delete_project' and 'delete_file', though it could be more specific about what constitutes a 'project file'.

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 tool vs alternatives like 'delete_file' or 'delete_project_folder'. The description does not specify context or exclusions.

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