scrape_stock

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

With no annotations, the description should disclose behavioral traits like network dependency, error handling (e.g., invalid symbol), rate limits, or data freshness. It only mentions the data source and parameters, leaving the agent uninformed about side effects or limitations.

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 concise and structured with an Args section. It is front-loaded with the purpose. Minor inefficiency: it could combine the first sentence with the args list without losing clarity, but overall it is well-organized.

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?

The description covers parameters and source, and an output schema exists to explain return format. However, it omits behavioral details (rate limits, error examples) and does not specify if data is real-time or historical. Adequate but with notable gaps.

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 0%, so the description must add meaning. It explains 'symbol' with examples, enumerates valid modes, and clarifies 'period' dependency on mode='history'. This is helpful, though it could clarify what 'profile' returns.

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 fetches stock market data from Yahoo Finance, and lists specific parameters with examples. Despite the verb 'fetch' rather than 'scrape', the purpose is unambiguous and distinguishes it from sibling tools which serve different domains.

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 versus alternatives. Sibling tools are unrelated, but there is no mention of prerequisites (e.g., requiring an API key) or context (e.g., real-time vs delayed data). The description assumes the agent knows when to fetch stock data.

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