deleteProjProject

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

No annotations are provided, so the description carries full burden. It discloses that the tool validates each project's status before deletion, which adds transparency. However, it does not explicitly state that deletion is irreversible or what happens to related data. Still, the description provides key behavioral context beyond just the action.

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, all essential. No filler. Front-loaded with the core action and endpoint. Every sentence adds value: batch delete, prerequisite, status condition, and validation behavior.

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 no output schema, the description covers the prerequisite, validation, and batch nature adequately. It lacks details on return value or error handling, but for a delete tool with clear constraints, it is sufficiently complete for an agent to use correctly.

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%, with per-parameter descriptions already covering origin from queryProjProjectList and status constraint. The description reinforces these points but does not add substantially new information beyond the schema. Baseline 3 is appropriate.

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 the resource '项目' (projects), specifying it is for batch deletion. It distinguishes from sibling tools like queryProjProjectList (query) and save/update tools, making the purpose unambiguous.

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 states the prerequisite: must call queryProjProjectList first and let user select projects. Also provides a clear condition: only projects with projectStatus 0 (未开始) can be deleted, and other statuses are not allowed. This gives strong guidance on when and when not to use the tool.

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