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 known. The description adds genuinely non-obvious scope information: sources are detached from the session but the underlying studies and files survive, which is exactly the distinction an agent needs before calling a destructive tool. It omits permission/org requirements and whether the clear is reversible.

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?

Two sentences, zero filler, with the destructive scope stated before the usage restriction. Every clause earns its place.

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?

An output schema exists and annotations cover safety, so the description only needs to convey purpose and blast radius, which it does. The one remaining gap is operational prerequisites for organization_id, though the schema points to list_organizations.

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 coverage is 50%: organization_id is documented in the schema, but session_id carries no description and the description only says "this Hub session" without noting the UUID format or that the session must already exist. The description adds almost nothing beyond the schema, which is the baseline expectation at this coverage level.

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 gives a specific verb and scope ("bulk removal" of "all sources from this Hub session") and distinguishes the operation from destructive file/study deletion. It does not explicitly name its closest siblings (remove_research_source, remove_research_study), but the word "all" versus a single source does the differentiating work implicitly.

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?

It states a clear condition ("Use only when the user requests clearing the session") and labels the tool "Legacy", which warns an agent to prefer newer paths. It never names the alternative tool to use instead, so the routing is implied rather than spelled out.

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