get_copy_trade_guide

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safe, static nature of the call is covered. The description adds nothing behavioral beyond that — no mention of what the guide contains, whether it is cached/versioned, or how large the payload is.

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 zero filler; the verb and resource come first and the platform scope follows. Nothing is padded or repeated.

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 simple single-param guide lookup with annotations covering safety, this is roughly adequate. However, with no output schema and no statement of what the guide covers or returns, an agent cannot anticipate the response shape before calling.

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 100% and the single 'chain' param has an enum with a per-value description, so the schema carries the load. The description's phrase 'Solana spot or HyperLiquid perp copy trading' restates the enum semantics (spot vs perp) but adds no new format or constraint detail.

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 ('Get a copy trading guide') and scopes it to Solana spot vs HyperLiquid perp copy trading, so an agent knows exactly what comes back. It does not explicitly distinguish itself from adjacent guide-style siblings such as get_trading_guide, get_component_guide, or get_skill_file.

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 guidance on when to reach for this guide rather than the many other copy-trade tools (get_copy_trade_list, create_copy_trade, get_copy_trade_wallets) or the other guide tools. No prerequisites, no exclusions, no alternatives named.

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