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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered. The description adds that it returns 'descriptive market data only' and 'returns everything in one payload,' which clarifies the scope and output shape beyond the annotations. No contradiction.

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 tight paragraph that front-loads the purpose, then lists the data contents, and ends with practical notes (no arguments, automation-friendly, descriptive only). Every sentence earns its place; there is zero fluff.

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 fully sufficient. It tells the agent what the payload contains, that it's one call, and that it's for recurring use. The output schema handles return-value details, so nothing else is needed.

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 has zero parameters and an empty schema, so the description has no parameters to explain. Baseline for zero-parameter tools is 4, and the description correctly notes 'No arguments' without adding unnecessary 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?

The description opens with 'One-call market brief' and enumerates exactly what it returns (BTC risk regime, news, whale buys/sells, Smart Money Radar, largest movers, liquidation picture). This is a specific verb+resource that clearly distinguishes it from the many targeted market tools in the sibling list, which are narrower. The agent knows this is the aggregate snapshot.

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?

It explicitly states 'for a scheduled or recurring run' and notes that it can be called on a timer, making the intended use case unmistakable. It doesn't name alternative tools for when a narrower brief would suffice, but the 'one-call' framing implies it's the comprehensive option, and the sibling list offers plenty of more granular counterparts.

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