getAdlAlert

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

With no annotations, the description fully discloses behavioral traits: data updates every 1 minute, no authentication required, optional symbol parameter retrieves all data, and explains key metrics (pnlRatio, insurancePnlRatio). No contradictions.

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?

Well-structured with sections and bullet points, but slightly verbose with repeated agent hint and data update frequency mentioned twice. Could be trimmed without losing clarity.

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?

Given no output schema and one optional parameter, the description covers all necessary context: purpose, usage guidelines, data freshness, parameter behavior, and alternative tools. No gaps.

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?

Only one parameter (symbol) with 0% schema description coverage. The description adds meaning by explaining omitting symbol retrieves all symbols, which is critical for usage. Baseline for 0 parameter descriptions is 4.

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 queries ADL alert data and insurance fund metrics for derivative contracts, listing supported products and distinguishing itself from getInsurancePool. The verb 'Query' and target resource are specific.

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?

Provides explicit use cases (monitor ADL risk, check insurance fund balance, understand thresholds) and an explicit when-not-to-use ('Do not use for general insurance pool balances — use getInsurancePool instead'). The agent hint reinforces this.

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