datafeed_config

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

Discloses full return structure and a known inconsistency (D vs 1D). No contradictions with readOnlyHint annotation. Adds context beyond annotations by explaining the resolution issue.

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?

Front-loaded with purpose. Some detail in listing types could be condensed, but overall efficient and informative. The note is essential and well-placed.

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?

With no parameters and an output schema, the description fully explains the return values and a critical caveat. No gaps remain for agent understanding.

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?

No parameters; schema coverage 100%. Baseline 4 per guidelines. Description adds no parameter info, but none needed.

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?

Clearly states 'Get the datafeed configuration: instrument types and resolutions.' Specifies exact return fields and their meanings. Distinguishes from sibling tool get_candles by noting resolution translation.

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 note about discrepancy between 'D' and '1D' and advises to use get_candles for friendly resolution values. Guides agent on when to use this tool (for config) and when to avoid raw codes.

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