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

The description adds behavioral context beyond the annotations by stating 'No arguments; returns everything in one payload' and 'Descriptive market data only.' This tells the agent this is a read-only, non-executing aggregate snapshot, reinforcing the readOnlyHint and destructiveHint. It does not detail output schema specifics, but the output schema exists, so the added context is sufficient.

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 two sentences, front-loaded with the core purpose and usage context, then lists the payload contents in a compact series. Every clause adds information, with no filler or repetition.

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 zero-parameter tool with an output schema, the description is complete: it defines when to use it, what it returns, that it is safe/descriptive, and that no arguments are needed. The absence of explicit return-field details is acceptable because the output schema exists.

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. The description explicitly confirms 'No arguments,' which is the only parameter-related information needed. Nothing is left ambiguous about the input surface.

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 states a clear purpose: a one-call market brief for scheduled or recurring runs. It enumerates the exact content (BTC risk regime, whale net flows, Smart Money Radar coins, biggest movers, 24h forced-close picture) and explicitly contrasts with a single-purpose tool by calling itself 'one-call' and 'everything in one payload.' This distinguishes it from the many focused sibling tools.

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 says this is for 'a scheduled or recurring run' and that 'an automation can ask it on a timer,' which gives clear context for when to use it. It does not explicitly name alternatives or when-not-to-use conditions, so it stops short of a full 5.

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