Delete project

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

No annotations present. The description does not disclose that deletion is permanent, whether it requires permissions, cascading effects on tasks, or recovery options. Entire behavioral burden is unmet.

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 (one line) but front-loads the HTTP method. However, 'Delete project' is redundant with the name. Could be more efficient by omitting redundancy.

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?

No output schema and minimal description. Fails to provide enough context about the operation, parameters, or expected behavior for correct usage.

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 0% and description does not explain the 'id' parameter or its type (project ID). Merely echoing the endpoint pattern without adding clarity.

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 'Delete project' and includes the HTTP method (DELETE) and endpoint pattern, clearly indicating the resource and action. Distinguishes from siblings like 'archive_project' by the delete verb.

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 versus alternatives like 'weeek_archive_project'. No prerequisites, consequences, or context for use provided.

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