minus_dm

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

No annotations are provided, so the description must fully disclose behavioral traits. It only states 'Fetch minus directional movement', which implies a read operation but lacks details on permissions, rate limits, output format, or any side effects. This is inadequate for a tool with multiple parameters and no output schema.

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 extremely concise with a single phrase, 'Fetch minus directional movement', which is front-loaded and wastes no words. However, this conciseness comes at the cost of clarity and completeness.

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 complexity (5 parameters, 3 required), no annotations, 0% schema coverage, and no output schema, the description is severely incomplete. It doesn't explain what the tool returns, how to interpret results, or provide any context for usage, making it inadequate for effective tool invocation.

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 0%, meaning parameters like 'symbol', 'interval', 'month', 'time_period', and 'datatype' are undocumented in the schema. The description adds no meaning about what these parameters do, their formats, or examples, failing to compensate for the lack of schema documentation.

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 'Fetch minus directional movement' restates the tool name 'minus_dm' with minimal elaboration, making it tautological. It doesn't specify what resource or data is being fetched beyond the name, nor does it distinguish this tool from sibling tools like 'minus_di' or 'plus_dm', leaving the purpose vague.

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 use this tool versus alternatives. With many sibling tools for technical indicators and financial data, there's no indication of context, prerequisites, or comparisons to help an AI agent choose appropriately.

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