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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds no behavioral context beyond the annotations — nothing about whether 'raw downloads' means large binary payloads, whether contacts are redacted, or how the response is shaped, despite having no output schema to fall back on.

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?

It is admirably short, but it is a bare fragment with no subject or verb, which makes it read like a field list rather than a tool description. Brevity here comes at the cost of a clear opening statement.

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 zero-parameter, output-schema-less tool, the enumerated content list partially substitutes for a missing output schema by telling the agent what to expect back. But the absence of any stated action, scope (all sources? per study?), or sibling relationship leaves it only minimally complete.

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?

With zero parameters the baseline is 4. However, the description is silent on the fact that this tool takes no arguments — an agent might expect to pass a source ID or study identifier — so a small gap remains.

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 is a noun phrase enumerating content ('Primary source URLs, verification timestamps and hashes, raw downloads and collaboration contact') rather than a verb+resource statement, so the agent must infer that the tool retrieves source/provenance records. It is distinguishable from data-oriented siblings like get_demographics or get_polls by subject matter, but it never states the action.

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 call this versus get_study, get_summary, or any other sibling. The agent is left to guess whether this is a provenance/citation lookup or something else entirely, and no prerequisites or exclusions are given.

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