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

The annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the description does not need to restate safety basics. It adds valuable scope context by clarifying that the underlying study or uploaded file is not deleted, which resolves what the destructive hint applies to. It could go further on permissions or session-state effects, but the key behavioral nuance is present.

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?

The description is two tight sentences, front-loaded with the core action and immediately followed by the non-deletion clarification. Every phrase contributes useful meaning with no 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?

Given the presence of an output schema and annotations covering safety profile, the description is largely complete: it specifies the identifier source and clarifies destructive scope. Minor operational details such as permissions, behavior when the session is inactive, or handling of a source not present in the session are not covered.

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 33%, so the description must compensate. It meaningfully explains source_id as an opaque ID from inspect_research_session and implies session_id via 'Hub session', but it does not explain organization_id or add constraints around session_id beyond what the schema already conveys.

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 states a specific verb ('Remove'), a specific resource ('one source'), the containing resource ('Hub session'), and the identifier origin ('opaque ID returned by inspect_research_session'). This clearly distinguishes it from clear_research_sources (all sources) and remove_research_study/delete_study (underlying study deletion).

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 gives a clear prerequisite for obtaining source_id via inspect_research_session, which tells the agent when and how to use the tool. It does not explicitly name alternatives such as clear_research_sources or remove_research_study, so it lacks full when-not/alternatives guidance.

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