yahoo_finance_screener_custom

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

No annotations provided, so description must disclose behavioral traits. 'Constrained' hints at limitations but no details. No mention of rate limits, data volume, or side effects.

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?

Single sentence is concise but under-informative. Could include more detail without becoming lengthy. Not overly verbose but not optimally structured.

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?

Severely incomplete for a tool with a complex object parameter and no output schema. Fails to explain the request shape, constraints, or return value. User cannot effectively craft a query.

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?

While schema coverage is 100%, the parameter description 'Custom screener request' is extremely vague. Adds no meaning beyond what the schema provides (that it's an object). Does not explain required fields, structure, or examples.

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?

Description uses verb 'runs' with resource 'constrained Yahoo Finance custom screener query'. The term 'custom' distinguishes it from sibling 'yahoo_finance_screener' (preset screeners). However, 'constrained' is vague and not explained.

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 guidance on when to use this tool vs alternatives like 'yahoo_finance_screener'. Does not mention prerequisites or context for using a custom screener.

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