Support Helena's free scientific infrastructure

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

The annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description adds valuable context beyond those: the action is opt-in, involves no payment or outreach, and changes no scientific result. This meaningfully clarifies what the tool will and will not do.

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 short and front-loads the core purpose in the first sentence. The second sentence adds useful safety/behavioral context, though some phrasing like 'the separate Helena Good MCP' is slightly awkward and could be tighter.

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 informational tool with a provided output schema, the description is largely sufficient. It covers purpose, the informational nature, and the no-payment/no-outreach guarantee. It could be slightly more explicit about when a user would want this information, but nothing critical is missing.

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 has zero parameters, so the parameter-semantics burden is minimal. The description does not need to explain any inputs, and the baseline of 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 states a clear action — 'Learn about the separate Helena Good MCP' — and clarifies that this tool is informational, not a payment or outreach mechanism. It is easily distinguishable from the sibling search/get literature tools, though it does not explicitly name any sibling or contrast itself.

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 implies the tool is for users who want information about supporting Helena, and it explicitly says no payment or outreach occurs. However, it does not state when to use it versus alternatives or mention sibling tools, leaving the routing decision mostly to inference.

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