get_stock_timeline

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

With no annotations provided, the description carries the burden of behavioral disclosure. It enumerates the data categories included, which is useful, but does not mention potential limitations such as data freshness, error behavior, or performance. It neither contradicts annotations nor provides deep transparency.

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 compact: two sentences and an arg list. Every sentence adds value—defining the tool's scope and purpose—without unnecessary fluff. The structured arg section is easy to parse.

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's low complexity (2 params, simple get operation) and the presence of an output schema, the description provides enough context: it lists the event types included and clarifies the tool's role. No additional explanation of return values is needed.

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 schema has 0% description coverage, but the description fully compensates by explaining both parameters: 'symbol' with NSE examples and 'max_events' as the max timeline events. This adds meaningful meaning beyond the schema's bare names and type.

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 explicitly states the tool provides a 'unified stock timeline' covering news, results, insider, bulk deals, sentiment, pledge, and smart money. It also frames it as the 'what changed recently?' tool, clearly distinguishing it from sibling tools like get_stock_brief or get_social_sentiment.

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?

The description gives a clear usage cue ('what changed recently?') that implies when to use this tool. However, it does not explicitly name alternative tools or state when not to use it, so it stops short of full exclusion guidance.

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