segnals_get_trades

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

With no annotations, the description adds some behavioral context: it requires auth scope 'read:stats' and implies recent data via 'recent trade history'. But it does not disclose data freshness, pagination limits beyond max, or rate limiting. Adequate but not thorough.

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?

Two sentences plus an example is generally concise. However, the sentence about filtering includes non-existent parameters ('symbol', 'date range'), making it inaccurate and wasteful. The example is helpful but could be better aligned with schema.

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 no output schema and 3 parameters, the description should explain return format or pagination behavior. It fails to do so, and the misleading filter list reduces completeness. The scope requirement is a plus, but overall the description leaves significant gaps for an agent.

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 covers all parameters (bot_id, limit, offset) with descriptions. However, the description mentions 'optional filtering by ... symbol, or date range' which are NOT present in the schema. This is misleading and directly contradicts the schema, thus adding no value and causing confusion.

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's purpose: 'Get recent trade history across all bots' with optional filters. The verb 'get' and resource 'trade history' are specific, and the scope is well-defined. It distinguishes from siblings like segnals_get_bot_performance and segnals_get_pnl_summary by focusing on individual trades.

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 includes usage guidance: 'Use this to review individual trades' and specifies a required scope 'read:stats'. However, it lacks explicit when-not-to-use instructions or mention of alternatives, which is somewhat expected given the sibling list.

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