getDelistedCompanies

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so the safety profile is covered. The description adds only the useful scoping fact that listings are US-exchange delistings; it says nothing about result ordering, pagination behavior, or data freshness beyond what the schema implies.

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 are short, but the opening 'Stay informed with the FMP Delisted Companies API' is marketing filler that carries no selection value. The substantive content arrives 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?

For a simple, optional-parameter list tool with no output schema and full annotation coverage, the definition is nearly sufficient; an agent could call it correctly. Only minor gaps around pagination and result ordering remain.

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 page and limit (including the max of 100) are already fully documented. The description adds no meaning about paging semantics or result ordering, which is the correct baseline when the schema does the work.

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 names a specific resource (companies delisted from US exchanges) and implies a list-returning read. It is distinguishable from siblings like getActivelyTradingList or getSymbolChanges, though it never explicitly contrasts with them.

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?

It gives a motive for use ('avoid trading in risky stocks and identify potential financial troubles') but no explicit when-to-use conditions, prerequisites, or named alternatives such as getSymbolChanges for ticker-change lookups.

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