getStockNews

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds that results come from 'a variety of sources' and lists the returned fields, but says nothing about result volume, pagination, or whether the feed can be narrowed by date or symbol — meaningful gaps given the schema exposes from/to/limit/page.

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?

Two short sentences, but the opening 'Stay informed with the latest stock market news using the FMP Stock News Feed API' is marketing framing rather than an action statement. The informative part — the returned fields — is buried in the second sentence.

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?

With no output schema, the description does useful work by naming the returned fields. However, it omits that the tool accepts date-range and paging parameters, so an agent reading only the description could wrongly conclude this is a fixed 'latest N articles' call and miss the filtering capability entirely.

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 description coverage is 100%, so the from_date, to, page and limit parameters are already documented in the schema. The description adds no interpretive detail — notably it frames the tool as returning only 'the most recent articles' and never hints that a date range (from_date/to) can be supplied, which is the one piece of meaning that would have helped.

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 identifies a specific resource — the latest stock market news feed — and enumerates what is returned (headlines, snippets, publication URLs, ticker symbols), which lets an agent distinguish it from getCryptoNews or getForexNews. It never contrasts with the very close sibling searchStockNews, so the differentiation is only partial.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no mention of alternatives. The phrase 'most recent articles' weakly implies this is for browsing the latest news rather than targeted queries, but with searchStockNews sitting right beside it in the toolset, that inference is left entirely to the agent.

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