get_instrument_breakdown

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, yet it says nothing about read-only safety, side effects, or data requirements. It does disclose the analytical payload (verdict categories, red flags), which is useful, but it omits how verdicts are derived and whether the call is expensive or cached.

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 single sentence is compact and front-loads the key content categories with no filler. However, it is so terse that it reads as a label rather than a structured explanation, and the lack of a leading verb slightly weakens orientation.

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?

An output schema exists, so return values needn't be explained, and parameters are fully documented. But with no annotations and no usage guidance, the definition is incomplete for distinguishing this analytical tool from overlapping siblings; an agent has no basis for choosing it over get_performance.

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% with three documented parameters, so the schema already explains the period window and date overrides. The description adds nothing about filtering semantics or default behavior beyond what the schema provides, making a baseline 3 appropriate.

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 names the resource (per-instrument breakdown) and enumerates the output content (verdict, best/worst sessions, insights, red flags), so an agent can infer what it produces. But it is a noun-phrase fragment with no verb, and it does not distinguish the tool from siblings like get_performance or get_behavior_report, both of which plausibly overlap.

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?

No when-to-use guidance, no prerequisites, and no mention of alternatives. The agent must guess whether to call this versus get_performance for instrument-level analysis. It also does not say whether it requires existing trade data or a minimum sample size for verdicts.

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