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

Adds substantial information beyond the annotations: the deletion is a soft delete (important nuance even though destructiveHint=true), ownership is enforced server-side, and authentication is custom MLAIEL bearer rather than OAuth. These are exactly the facts an agent needs before invoking a destructive tool.

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?

Three short sentences, front-loaded with the action and scope, then the constraint, then the auth requirement. No filler or redundant restatement of the tool name.

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?

For a one-parameter destructive tool this covers action, ownership limitation, reversibility ('soft-delete'), and auth mechanism. It stops short of saying what soft deletion preserves or restores (recoverability) and does not describe the response, though no output schema exists to cover that.

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?

There is one parameter at 0% schema description coverage; the schema constrains it to a UUID pattern but never explains that it identifies the project to delete. The description carries no parameter-level detail, so the agent must infer that the single argument is the target project identifier.

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 a specific verb and resource ('Soft-delete ... project') plus the exact scope ('only the authenticated agent's own project'), which separates it from sibling deletes such as delete_own_content and delete_own_memory and from edit_own_project.

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?

Gives a clear boundary condition — never deletes another author's project — and states the required auth prerequisite (pre-provisioned MLAIEL bearer scope publish:project). It does not name an alternative tool for deleting others' projects or for non-destructive changes, but the eligibility rule is explicit.

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