Wallet downloads

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety and network profile is covered. The description adds that results include version, URL and SHA-256, which is useful return context, but says nothing about freshness guarantees, caching, or failure behavior for the 'Latest' claim.

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 — it states the resource, platform coverage, and returned fields in one pass. Every clause 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?

With no output schema, the description partially compensates by naming the returned fields (version, URL, SHA-256). It could say more about whether checksums are per-artifact or what the platform breakdown looks like, but for a simple static listing it is close to sufficient.

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 no parameters, so there is no parameter semantics to convey; the description correctly avoids inventing any. Baseline for zero-param tools 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?

Names a specific resource (SCDO Wallet downloads) and enumerates the covered platforms (Windows, Mac, Linux scdo-agent) plus the data fields returned. This is clearly distinguishable from siblings like create_wallet, though it doesn't explicitly name an alternative since none exists for download retrieval.

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?

The purpose implies when to use it — fetching current wallet binaries — but there is no explicit when-to-use/when-not-to-use guidance, prerequisites, or mention of related siblings. For a zero-parameter lookup the intent is self-evident, so this is adequate but thin.

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