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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description adds genuinely non-redundant behavior by disclosing that this is a soft delete, telling the agent the record is not physically erased and is likely recoverable. It stops short of saying what happens to linked contacts or whether elevated 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?

One short sentence with the verb first and the soft-delete qualifier in parentheses, so no reading time is wasted. It is terse rather than padded, though it leaves too much unsaid for a destructive mutation.

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 operation with full annotation coverage and no output schema, the core is present. Missing pieces are the side effects on contacts/links and the identifier source, which matter for a mutation in a networked care-organization domain.

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?

The single parameter organizationId has no schema description (0% coverage) and the description never mentions it, where the identifier comes from, or whether it accepts names/slugs. Only the schema's uuid type and pattern constrain the value, so the description compensates for nothing.

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 ('Remove an organization') and scopes it to the care network, which distinguishes it from vitalli_update_organization and vitalli_delete_contact by name. It does not explicitly name the sibling an agent should use for a non-deleting alternative, but the operation itself is 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?

There is no guidance on when to use this versus vitalli_update_organization (e.g., deactivation) or what preconditions must hold before removing an org. The agent must infer usage entirely from the tool name.

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