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

With no annotations provided, the description carries the full burden and does substantial work: it discloses that the desk is live and not fixed, that anyone with fills or closed trades receives a weight, that named handles are aliases, and that data comes from a fan-in of live trades, DexScreener, Robinhood chain, and X socials. It also flags 'autobuy names' as what the wallet copies, which is useful behavioral context.

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 compact and front-loaded with the core concept, then adds aliases, weighting, data sources, and a caveat. Each sentence adds information, though the 'Not financial advice' boilerplate is conventional rather than functional and the jargon is dense.

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?

Given there are no parameters and no output schema, the description gives a reasonably complete picture of what the tool represents: a live, weighted, multi-source desk with alias handling. It could be more explicit about the exact shape of the returned data, but for a zero-parameter live-view tool it provides enough context for an agent to select and invoke it.

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 accepts zero parameters and the empty input schema fully captures this. The description's job is therefore not to explain parameters, but to explain what the parameterless tool returns, which it does.

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 identifies the tool as a 'live desk' of currently profitable FOMO traders, with named handles as aliases and weights based on fills or closed trades. It does not use an explicit verb like 'returns' or 'lists', and relies on insider jargon, but the resource and scope are specific enough to distinguish it from a vague catch-all.

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 description implies when to use the tool: when you want the current, dynamically weighted set of active printers rather than a fixed eight. However, it does not explicitly state alternatives, exclusions, or when not to use this tool, 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.