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

Annotations include readOnlyHint and openWorldHint, and the description adds valuable behavioral context: risk calculations are approximate and treat all positions as isolated-margin regardless of actual margin mode. It also discloses the circuit-breaker statuses. This goes beyond the annotations without 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?

Two sentences efficiently convey the tool's purpose, key analysis components, behavioral caveat, and output statuses. Every element earns its place, and the description is front-loaded with the core purpose.

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 complex analytical tool with no output schema, the description provides a solid overview of the analysis dimensions and resulting statuses. It could have elaborated on the exact output format or dependencies between parameters, but given full schema coverage and annotations, it is sufficiently complete for an agent to understand scope.

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?

Schema description coverage is 100%, so all parameters are individually documented. The description does not add additional meaning to specific parameters beyond what the schema provides, such as relationships or calculation impact. Baseline 3 is appropriate given full schema coverage.

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 clearly states the tool analyzes Binance Futures long-grid risk and lists specific components (core grid math, Market Regime context, Top-Trader/OI squeeze risk, dynamic stress, circuit-breaker decision). It distinguishes from sibling data-retrieval tools by describing a composite risk analysis with explicit outcome statuses.

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 usage for long-grid risk analysis but provides no explicit guidance on when to use vs alternatives or when not to use. It lacks references to alternative tools or exclusions, leaving the agent to infer context from the title and description.

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