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

Annotations already cover the safety profile (readOnly=true, idempotent=true, destructive=false, openWorld=true), lowering the burden. The description adds a genuinely important behavioral fact not in the annotations: the $5.00/call cost, which materially affects invocation decisions, plus the breadth of the returned pack. It stops short of rate limits or output format specifics, so 4 rather than 5.

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 sentence that front-loads the cost and then lists the pack contents; no filler or redundancy. It is efficient, though the feature list is dense and could be structured more scannably.

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 a zero-parameter schema, an existing output schema, and annotations covering the safety profile, the description's main job is to convey scope and cost, both of which it does. The one remaining gap is relative positioning against the twelve sibling tools, which it never addresses.

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 are zero parameters, so the baseline is 4 and there is no schema-level parameter meaning to add or compensate for. The description correctly says nothing about inputs, which is appropriate here.

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 concrete deliverable ("Full machine-readable research pack") and enumerates its contents: expanded official evidence, global news, graph relationships, price lags, and commercial opportunity analysis. That is a specific resource description. It does not, however, differentiate this tool from the many similarly named siblings (e.g., shadowgraph_global_brief, shadowgraph_opportunity), so it lands at a clear-but-undifferentiated 4.

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 only usage-oriented signal is the price ("Paid ($5.00/call)"), which implies a cost tradeoff but never says when to choose this over shadowgraph_free_preview or the other briefs. No when-to-use, when-not-to-use, or alternative-naming is provided, so this is essentially absent guidance.

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