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

Annotations already declare destructiveHint=true, idempotentHint=false and readOnlyHint=false, so the safety profile is covered. The description earns credit for adding real behavioral detail beyond that: deletion is a soft hide (hidden=true) and the actual removal runs as an asynchronous background DeleteAppJob. It does not say whether or how the hidden project can be restored.

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?

One sentence, front-loaded with the action and immediately followed by the mechanism. Zero filler.

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 mutation with full annotation coverage and no output schema, the description supplies the mechanism an agent needs (soft delete plus async job). It stops short of saying what the call returns or whether the hidden project is recoverable, which would complete the picture.

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 100% and the single app_id parameter is documented with a useful provenance hint ('from list_projects'). The description adds no additional parameter meaning, so the baseline 3 applies.

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+resource ('Delete a project') with an unambiguous resource name that maps cleanly onto the create_project/update_project/get_project/list_projects family. It doesn't explicitly call out siblings such as delete_portal or update_project, but the resource naming alone differentiates it.

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?

Usage is implied by the verb — call it when a project should be removed — but there is no explicit when-not guidance or pointer to an alternative (e.g., update_project for reversible hiding). The parenthetical hint that deletion only sets hidden=true lets a careful agent infer that other paths exist, but it isn't stated as guidance.

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