binance_us_cl_alert_history

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes what the tool returns (detailed alert records with specific fields), its specialized use case (credit line accounts with institutional agreements), and the nature of the data (historical alerts for risk analysis). It doesn't mention rate limits, authentication needs, or pagination behavior, but provides substantial operational context.

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 well-structured and efficiently organized: purpose statement, critical warning, alert type definitions, record structure details, and use cases. Every sentence adds value with no redundancy. The warning is appropriately front-loaded with an emoji for emphasis.

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 read-only historical data tool with no output schema, the description provides excellent context: it explains what data is returned, the record structure, use cases, and critical prerequisites. The main gap is the lack of information about response format (e.g., pagination, error handling), but given the tool's relatively straightforward nature and comprehensive parameter documentation, this is a minor omission.

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 schema has 100% description coverage, so parameters are well-documented in the structured schema. The description doesn't add parameter-specific information beyond what's in the schema, but it does provide context about alert types (MARGIN_CALL vs LIQUIDATION_CALL) that helps interpret the 'alertType' parameter's enum values.

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's purpose: 'Get margin call and liquidation alert history for credit line account.' It specifies the exact resource (alert history) and distinguishes it from siblings like 'binance_us_cl_liquidation_history' by focusing on alerts rather than just liquidations.

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 provides explicit context for when to use this tool ('Review past risk events', 'Understand account risk patterns', 'Audit margin call history') and includes a critical prerequisite warning ('⚠️ REQUIRES INSTITUTIONAL CREDIT LINE AGREEMENT'). However, it doesn't explicitly state when NOT to use it or name specific alternatives among the many siblings.

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