Metis — Remove Project

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

Describes what gets deleted (record, tasks, optionally folder) and the safety check. No annotations provided, so burden is on description. Lacks disclosure of irreversibility, required permissions, or response format. Output schema exists but not detailed.

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?

Extremely concise with a clear structure: brief intro, bulleted effects, Args section. No wasted words or 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?

Covers key behavioral aspects (deletion scope, file safety check) and parameter details. Could add irreversibility warning or permission requirements, but output schema likely covers return structure. Effective given tool complexity.

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 0%, but description adds meaningful context for both parameters: project_id identifies the project, delete_files explains behavior and default value. Adds safety constraint for file path.

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?

Clearly states the tool removes a project entirely, deleting the project record and associated tasks, with an option to delete files. Distinguishes from siblings like archive_project and delete_task by specifying destructive action.

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 describes when to use (permanent removal) and includes a safety check for file deletion. Does not explicitly state when not to use or compare to alternatives like archive_project, but the context is clear.

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