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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered. The description adds real value beyond that by disclosing the cascade: revisions, relations, signatures, and baseline references are also removed, which an agent cannot learn from the annotations. It omits whether the delete is reversible, whether it fails when other objects reference the concept, and what confirmation or permissions are required.

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?

A single sentence with no filler, and the destructive scope is front-loaded right after the verb so the agent sees the blast radius immediately. Nothing could be trimmed without losing information.

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 delete with no output schema and annotations that already flag destructiveness, the definition covers the essential unknown: what else gets removed. Missing only secondary details such as irreversibility and error behavior for dangling references.

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 a single required parameter with 100% schema description coverage, so the baseline is 3. The description adds no meaning beyond the schema — nothing about ID format, whether an ID can be obtained from list_concepts, or what happens with an unknown ID.

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 pairs a specific verb ("Delete") with a specific resource ("a concept") and enumerates the cascade scope: revisions, relations, signatures, baseline references. That is clearly distinct from delete_relation, delete_project, and update_concept in the sibling list. It stops short of explicitly naming a sibling to contrast with, which keeps it at 4 rather than 5.

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?

There is no guidance on when to use this versus update_concept or delete_relation, no statement of prerequisites or permissions, and no warning about irreversibility. The agent must infer that this is a terminal operation from the word "Delete" alone.

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