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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false), so the burden is lower. The description still adds real behavioral context by stating the data is assembled from existing evidence readers and that unavailable components are explicitly labeled, which tells the agent to expect partial results rather than a hard failure. It does not mention latency, caching or auth, but the partial-result disclosure is the most valuable trait it could have surfaced.

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?

One tightly packed sentence with no filler, and the component list is front-loaded before the caveat about labeled-unavailable data. Slightly dense for a single sentence, but every clause carries information.

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 composite tool with no output schema, the description should convey more about the shape of the returned packet, such as whether components are keyed objects or flat fields and what 'labeled' looks like. It enumerates the four components adequately but leaves the return structure to discovery.

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?

There is a single required parameter with 100% schema description coverage ('Perp symbol, e.g. BTCUSDT'), so the schema does the work. The description adds nothing about symbol semantics, such as whether unknown symbols fail or return labeled-unavailable components, so baseline 3 is appropriate.

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 names a specific resource (an evidence packet) and enumerates its contents: liquidation magnets, historical reach, venue structure and feed trust. That is far more concrete than the title 'Evidence packet' alone. It stops short of explicitly distinguishing itself from siblings that each return one component (get_liquidation_magnets, get_reach_stats, get_feed_trust), leaving the aggregation role to be inferred.

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?

Usage is only implied: an agent can deduce this is the composite call that bundles several evidence readers, but the description never says when to prefer it over the individual sibling tools or what it costs to call it. No exclusions, prerequisites or alternatives are named.

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