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

Annotations already establish readOnlyHint and destructiveHint=false, so safety is covered. The description adds real context beyond them by disclosing the member-safe redaction policy: private wallet, contributor and diagnostic fields are stripped, which tells the agent what data shape to expect.

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 front-loaded sentence with no filler; the scope claim comes first and the redaction detail second. The semicolon clause is slightly dense but earns its place.

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?

Output schema covers the return shape and annotations cover safety, so the description needn't restate those. The remaining gap is sibling disambiguation: an agent picking between get_alpha, get_alpha_launch and this feed gets no guidance from the text.

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, so the baseline is 4. Nothing parameter-related needs explanation, and the description correctly spends its words elsewhere.

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 resource: 'Read the ... Alpha Surge evidence feed.' The named feed distinguishes it from most siblings, but it never differentiates itself from the near-identical get_alpha and get_alpha_launch, which an agent could easily confuse it with.

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?

No when-to-use, when-not-to-use, or alternative is given. With three alpha-family siblings (get_alpha, get_alpha_launch, get_alpha_surge), the description leaves the selection decision entirely to inference from the tool name.

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