recAuroraHomeAIParams

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

Discloses rate limit (20 req/s per UID per path), maximum returned strategies (18, 6 for Copy Trading), and that strategies are mixed across bot types. With no annotations, the description carries full burden; it could mention read-only nature, but overall sufficient.

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?

Concise at ~5 sentences, front-loaded with purpose, and each sentence adds value (purpose, composition, rate limit, usage hint). No redundancy.

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?

Covers purpose, output characteristics, rate limit, and usage context. Lacks explicit statement about read-only nature, but given no output schema and simple parameterless design, it is fairly complete.

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 coverage is 100% (no parameters), and description explicitly states 'The request takes no parameters,' adding meaning. It also explains the output (biz_type field), surpassing the empty schema.

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 it returns a curated list of Aurora AI strategy recommendations for the home feed, mentioning mixed bot types and referencing the biz_type field. This distinguishes it from siblings like recAuroraCreationAIParams (which likely deals with creation) and recExploreStrategy.

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 agent hint: 'Use this when a user opens the trading-bot home page and wants to see what Aurora is currently recommending.' It also gives next steps (pass aurora_id to info endpoint). However, it does not specify when not to use this tool or contrast with alternatives.

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