getLatest8KFilings

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, openWorldHint), so the burden is lower. The description adds meaningful domain context about what an 8-K covers, but its 'real-time access' and 'stay up-to-date' framing sits awkwardly with a tool that requires explicit from_date/to bounds, and it says nothing about result ordering, volume, or pagination behavior beyond what the schema declares.

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 sentences, front-loaded with the core action, with no repetition of the tool name. Some marketing padding ('Stay up-to-date with', 'using the FMP Latest 8-K SEC Filings API') could be cut without losing information.

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 date-windowed list endpoint with a fully documented schema, fully declared annotations, and no output schema, the description is minimally adequate. It still leaves an agent guessing on scope (all companies vs. one), result ordering, and how this differs from the cluster of neighboring filing tools.

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 all four parameters (from_date, to, page, limit) are documented in the schema itself. The description adds no meaning beyond that — no date-window limits, no default page size, no interaction between limit and pagination. Baseline 3 applies when the schema does the heavy lifting.

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?

States a specific verb and resource: retrieves the most recent 8-K SEC filings. The example event types (mergers, acquisitions, leadership changes) confirm the resource is 8-K material-event filings rather than general filings, which distinguishes it in substance from siblings like getLatestFinancialFilings or getFilingsByFormType, though it never names those siblings explicitly.

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 when-to-use guidance at all. Given the many adjacent filing tools in the sibling list (getLatestFinancialFilings, getFilingsByFormType, getFilingsBySymbol, getSecFilingExtract), the description should say why an agent picks this one — for example, that it returns all companies' 8-Ks in a date window rather than filtering by symbol or form type. Nothing here implies that.

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