get_signals

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

The description states it is a read operation ('get') and requires an API key, which provides some behavioral context. However, with no annotations provided, it lacks details on rate limits, error handling, or data format in the response. The bar is higher without annotations, and this is insufficient for full transparency.

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 a single, compact sentence that efficiently conveys the tool's purpose and a key prerequisite. There is no redundancy, and every word contributes value.

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?

Despite good schema coverage and conciseness, the description omits important contextual details such as the return structure, behavior when no signals exist, and error handling. For a tool with moderate complexity and no output schema or annotations, this is incomplete.

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 input schema already has 100% description coverage for all three parameters. The description adds minimal extra meaning beyond stating the API key's origin. Thus, it meets the baseline of 3.

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 the tool retrieves today's buy/sell signals for a specific strategy. The verb 'get' and resource 'buy/sell signals' are specific, and the scope ('today's', 'for a strategy') distinguishes it from sibling tools like list_strategies or get_strategy_performance.

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 mentions a prerequisite (API key from register_trial), which is helpful. However, it does not provide guidance on when to use this tool versus alternatives like compare_strategies or get_index_data, nor does it specify when not to use it.

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