get_adx

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

With no annotations provided, the description carries the burden of behavioral disclosure. It does add the prerequisite of an active broker session or specific broker, which is useful, but it does not mention whether the operation is read-only, what data is required, or any error conditions. The description is factual about the data source but lacks depth.

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 a single, front-loaded sentence with no redundancy. Every word contributes meaning, achieving high conciseness.

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 the tool's moderate complexity (six parameters, no output schema), the description provides the essential purpose and a key prerequisite (active broker/session) but lacks information about return format, parameter interactions, or potential errors. It is adequate but not comprehensive.

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?

All six parameters are fully described in the schema (100% coverage), so the baseline is 3. The description adds minor semantic value by indicating that the 'symbol' and 'broker' parameters relate to the symbol and broker context, but it does not elaborate on period, interval, or date ranges beyond what the schema already provides.

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 identifies the tool as retrieving the ADX indicator for a given symbol, using a specific verb and resource. The expansion of the acronym and mention of broker context distinguish it from other indicator 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 provides no guidance on when to choose ADX over other indicators like RSI or MACD, nor any exclusions or alternatives. The only usage context is the need for an active broker session or specified broker, which is implied by 'from active or specific broker in your session'.

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