get_company_news

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

With no annotations provided, the description alone must convey behavioral context. It details the return format (JSON string with headlines, summaries, URLs), but does not disclose limitations, error conditions, rate limits, or explicit read-only guarantees. For a simple news retrieval, this is adequate but not comprehensive.

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 well-structured. It front-loads the primary purpose, then lists parameters with clear formatting and finally describes the return value. Every sentence adds value with no redundancy.

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?

For a simple tool with 3 string parameters and no output schema, the description covers all essential aspects: purpose, parameter meanings, and return value format. It is complete enough for an agent to select and invoke the tool correctly without additional clues.

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 zero description coverage, but the description fully compensates by explaining each parameter: symbol with an example (AAPL), and from_date/to_date with format guidance (YYYY-MM-DD). This adds significant meaning beyond the bare schema.

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's function: 'Get news for a specific company over a date range.' It uses a specific verb (Get), identifies the resource (company news), and differentiates from sibling tools like get_market_news by emphasizing company-specificity.

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 context is clear: use when you need news for a particular stock symbol over a date range. It implicitly distinguishes from get_market_news, but lacks explicit guidance on when not to use or alternative tool references.

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