get_token_image

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description's 'server-rendered ... image metadata' subtly clarifies that this returns metadata rather than a raw image, which is useful, but it says nothing about the response shape, whether an image URL is included, or CDN/caching behavior.

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 tight sentence with no filler and the key qualifier ('server-rendered', 'metadata') up front. Nothing wasted, though it is arguably too terse to carry the tool's semantics.

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 two-required-parameter tool with no output schema and zero schema description coverage, the description leaves both parameter semantics and return content unexplained. Only the annotations carry the operational profile, and the gaps are material.

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?

Schema description coverage is 0% and neither parameter is described in the description. The tool requires tokenAddress and chain, yet the description never mentions either, and notably does not clarify the accepted chain identifier format (string or number per the schema).

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 ('Get') and a precise resource ('server-rendered token social-card image metadata'), which is distinctive among the get_* token siblings. It does not explicitly contrast itself with any sibling, but the resource is narrow enough to be unambiguous.

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 indication of when to use this tool versus alternatives such as get_token_details or get_token_trades, no prerequisites, and no exclusions. The agent is left to infer usage entirely from the resource name.

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