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

Annotations already declare destructiveHint=true, idempotentHint=true, openWorldHint=false and readOnlyHint=false, so the safety profile is known. The description adds a user-consent guardrail, which is genuinely useful, but says nothing about whether deletion cascades to studies/outputs or is recoverable — the details an agent most needs before calling 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?

One short sentence with the destructive verb front-loaded and the consent condition attached. Nothing is wasted, though the single sentence is doing very little work for a destructive two-parameter operation.

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 an irreversible destructive mutation with a half-documented schema, the description should say what is removed with the session and how to identify the target. An output schema exists, so return values needn't be explained, but the preconditions and blast radius are missing.

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 only 50%: organization_id is documented in the schema, but session_id has no description anywhere. The description mentions 'organization' context but never explains how to obtain a session_id (inspect_research_session, create_research_session, etc.), so it fails to compensate for the gap.

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?

A specific verb (Delete) plus a specific resource (organization Hub session) with a clear cardinality constraint ('one'). It does not, however, distinguish itself from the many other delete_* siblings (delete_study, delete_interview, delete_research_output), so an agent must infer the boundary.

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?

The phrase 'only when the user explicitly requests it' is a real usage gate that tells the agent not to delete proactively. But it offers no alternative path (e.g., inspect_research_session to confirm the target, or delete_study for a narrower deletion), which matters given the large delete-heavy sibling set.

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