get_edge_by_market

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

No annotations are provided, so the description carries the full behavioral burden; it does disclose the return fields (win rate, average PnL, profit factor, trade count). However, it omits any auth/permission notes, whether the read is scoped to an account by default, or how multi-account aggregation behaves, leaving meaningful gaps for a no-annotation tool.

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 header plus 'Best for/NOT for' structure is well front-loaded, but five example questions (including one in Hindi/Urdu) are surplus and border on padding. Core content is efficient; the example block is bloated.

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?

With no output schema, the description appropriately enumerates the returned metrics and all parameters are optional/covered, so an agent can call it correctly. It lacks only minor details such as default date-window behavior when date_from/date_to are omitted.

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 description coverage is 100%, so the five parameters are already documented in the schema, establishing a baseline of 3. The description adds little parameter-level meaning, and its market list ('PSX') even diverges from the schema enum values (FOREX, CRYPTO, STOCKS, FUTURES), a minor inconsistency.

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?

States a specific verb ('Compare trading edge and profitability') and resource ('broken down by market type: Forex vs Crypto vs Stocks vs Futures vs PSX'), then names returned metrics. It explicitly differentiates itself from the sibling get_edge_by_direction.

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 'Best for' and 'NOT for' sections, routing the agent to get_edge_by_direction for trade-direction questions. The when-to-use vs when-not-to-use distinction is unambiguous.

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