get_available_strategy_list

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

With no annotations, the description must carry the full behavioral burden. It does not disclose whether the operation is read-only, safe, or if it has side effects. It simply describes the output without addressing authentication, rate limits, or data freshness.

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 concise with three sentences: purpose, parameter, and return. It is front-loaded with the core functionality. Could include a brief note on usage, but overall it is well-structured.

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 has a single optional parameter and an output schema exists, the description is minimally adequate. It states the return type ('complete catalog') but lacks details like pagination, sorting, or whether the list is real-time. It does not leverage the output schema to reduce ambiguity.

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 description adds meaning for the single parameter 'response_filter' by specifying the accepted values ('full' or 'display'), which is absent from the input schema. This helps the agent understand how to use the parameter, though it does not explain what each value returns.

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?

Description clearly states 'Get all available DCA bot trading strategies.' This is a specific verb and resource, and it distinguishes from sibling tools which focus on accounts, balances, markets, or individual bot details.

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?

No guidance on when to use this tool vs alternatives. The description does not mention any preconditions, exclusions, or suggest alternative tools for different needs. It only states what the tool does.

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