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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false, so the mutation and its safety profile are known. The description adds useful scope ('every currently available study', legacy label) but does not say what happens to studies already in the session or whether repeats duplicate entries, which matters given idempotentHint=false.

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 short sentences, front-loaded with the legacy/scope caveat and followed by the disambiguation pointer. Nothing is wasted.

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?

The output schema exists, so return values need not be explained, but for a non-idempotent bulk mutation the description should cover duplicate handling and the redundant-add case. Permission or session-state prerequisites are also unaddressed.

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 only 50%: session_id carries no description and the description does not explain it beyond the loose phrase 'this Hub session'. organization_id is documented in the schema with a pointer to list_organizations, so the description adds nothing the schema doesn't already provide.

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 scope ('add every currently available study to this Hub session') and contrasts it with the alternative bulk-vs-single path. An agent can tell this apart from sync_research_study and remove_research_study without opening schemas.

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?

Explicitly names the sibling to use instead for a single study ('Use sync_research_study for a selected study'), giving a clear bulk-vs-single decision rule. It stops short of saying when this legacy path should be avoided altogether.

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