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 only the inventory of returned resources (campaign, rules, manifest, connection URLs), with no mention of auth prerequisites, freshness, or whether the URLs expire. Modest added value beyond annotations.

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?

A single compact sentence with no filler, and the verb comes first. It could be tightened only by making the domain clear rather than by removing words.

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, so return-value explanation is unnecessary, and there are no parameters to document. The remaining gap is motivational: for a marketing/funding-flavored tool sitting among gene and variant tools, the description never says why or when an agent would invoke it, which is the main thing left unexplained.

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?

The tool takes zero parameters and the schema is fully described, so there is nothing for the description to disambiguate. Baseline 4 applies.

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 verb ('Retrieve') and enumerates resources (campaign, rules, manifest, MCP connection URLs), so it is more than a restatement of the name. However, terms like 'Helena Good campaign' and 'manifest' are opaque in a dataset of genomics tools, and the title's framing ('Support Helena's free scientific infrastructure') only hints at the actual purpose. An agent can tell it apart from siblings but cannot easily form a mental model of what the returned object represents.

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 indication of when an agent should call this tool, whether it is required for setup/connection, or what alternatives exist. It is not misleading, but usage is left entirely to inference from the title.

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