destroy_projectsSoft-archives a project (sets is_archivied=true) instead of hard-deleting it, so historical tasks keep resolving and it can be restored later. Archived projects drop out of the default project list.
| Name | Required | Description | Default |
|---|---|---|---|
| body | Yes | ||
| kwargs | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description directly contradicts the destructiveHint=true annotation by stating this is a soft-archive, not a hard delete, and can be restored later. This is a clear contradiction, so the score is 1 regardless of other useful details.
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 two sentences, front-loaded with the most important behavior (soft-archive not hard-delete), and contains no fluff. It is concise and well-structured.
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?
While the behavior is described well (soft-archive, restorable, drops out of default list), the description omits return values, prerequisites, and parameter details. Additionally, the annotation contradiction undermines the overall completeness for a mutation tool.
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% per the context, and the description does not explain the meaning of company_id or pk beyond what the schema already states. The description adds no parameter-specific guidance, failing to compensate for the lack of coverage.
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 tool soft-archives a project by setting is_archivied=true, using a specific verb and resource. It distinguishes itself from hard deletion, making its 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?
It provides clear context on when to use it (when you want to preserve history and allow restoration) and contrasts with hard-deleting. However, it does not explicitly name alternative tools or state when not to use this tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools are clearly scoped to a specific resource and action, but a few near-overlapping pairs (e.g., list_attachments vs list_taskattachments, create_tasktags vs add_tag_tasks) could cause misselection without close reading. Descriptions are detailed enough to resolve most ambiguity.
The dominant verb_noun CRUD pattern (create_, list_, retrieve_, update_, partial_update_, destroy_) is consistent and predictable. However, non-standard pluralizations (companys, resumeentrys, taskdependencys) and a handful of irregular names (task_assign_user, move_relate_to_tasks) introduce minor inconsistencies.
With 83 tools, this server is far beyond a well-scoped MCP surface, even for a feature-complete project management suite. The sheer volume will overwhelm agents and make selection inefficient, clearly falling into the extreme-mismatch range.
The toolset provides thorough lifecycle coverage across companies, projects, tasks, sprints, attachments, comments, dependencies, tags, reminders, resume entries, tickets, and users. Missing operations like company deletion or task-attachment creation appear intentional and are worked around via existing tools.