recAuroraCreationAIParams

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

The description includes a rate limit (20 requests/second/UID/path) which is a useful behavioral disclosure. Since annotations are absent, the description carries the full burden; it does not mention error handling or empty results, but for a read-only query, the disclosure is adequate.

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 very concise: three short paragraphs covering purpose, rate limit, and usage hint. No redundancy and 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?

The description covers purpose and usage but lacks detail on the data structure (output has no schema) and does not explain the biz_type enum mapping. For a tool with 2 params and no output schema, more information about return data format and enum values is needed.

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 gives examples (SPOT_GRID, BTCUSDT) but the schema uses numeric enums for biz_type (0-8) without explaining the mapping. This mismatch confuses the agent. Schema coverage is 0%, and the description does not clarify the enum values or the meaning of symbol beyond an example.

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 that the tool returns recommended strategies and market mode for bot creation given biz_type and symbol. It distinguishes from sibling tools by specifying the exact context (bot creation page) and output (up to 6 strategies, market_mode).

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 agent hint explicitly states when to call this tool (when user is creating a bot and knows bot type and trading pair) and how to use the returned data (pre-select grid direction, present strategies as starting params). It provides clear, actionable guidance.

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