get_stock_brief

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

With no annotations, the description must carry the transparency burden. It discloses the output structure and data source (real Indian market data), but does not mention read-only safety, latency, data freshness, or any side effects. This is adequate for a getter tool, but not exhaustive.

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 well-structured with bullet points for the six personas and output sections. It is somewhat embellished with the 'Rs500Cr fund meeting' analogy, but the core content is efficient and earns its place. A small reduction for the non-essential metaphor.

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 simple schema (one param) and no annotations, the description provides a detailed account of the output structure and the analysis methodology. It covers the input parameter sufficiently and outlines return keys. It lacks any limitations or prerequisites, but overall it is complete enough for an agent to invoke correctly.

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 provides only a bare 'symbol' property with 0% description coverage. The description fully compensates by stating 'symbol: NSE stock symbol (e.g. RELIANCE, TCS, HDFCBANK)', giving source, type, and concrete 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?

The description explicitly states 'Multi-agent AI stock brief: 6 personas debate whether to BUY, HOLD, or SELL' and details the six analytical perspectives. It clearly distinguishes this from sibling tools like stock_quote or technical_indicators by describing a consensus-based multi-agent output.

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 provides clear context for when to use this tool: to get a comprehensive consensus on an NSE stock from multiple expert personas. It does not explicitly state alternatives or exclusions, but the context is strong enough to infer the appropriate use case.

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