find_breakouts

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

With no annotations and a sparse description, behavioral traits are almost entirely undisclosed. The description does not indicate whether the tool is read-only, destructive, or has other constraints, leaving the agent uninformed.

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 sentence, which is concise but lacks necessary detail. It is too brief to be useful, sacrificing completeness for brevity.

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 the tool has 5 parameters and an output schema, the description is severely incomplete. It does not explain how parameters affect results, what the output contains, or the kind of breakout detection algorithm used.

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 has 0% description coverage, and the tool's description adds no explanation for any of the 5 parameters. Parameter meanings like max_rsi, min_rsi, max_results, exclude_symbols, and min_trend_score remain unclear from the description.

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 mentions 'breakout discovery and candidate surfacing' which gives a general sense of purpose, but it lacks specificity about what kind of breakouts and does not distinguish the tool from similar siblings like get_trend_score or screen_stocks.

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 usage guidelines are provided. The description only states that a paid Fintools MCP is required, but does not indicate when to use this tool versus alternatives or any prerequisites beyond payment.

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