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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions retrieving a list but does not disclose pagination, rate limits, output format, scope (e.g., US vs global), or whether the list is static or dynamic. The language is promotional rather than informative, lacking concrete behavioral details.

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 only two sentences, but it is padded with filler phrases like 'Easily retrieve' and 'helping you explore the full range of available securities,' which add little substantive information. It is adequately sized but not tightly written; each sentence could be more direct.

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?

This is a simple no-parameter list-retrieval tool, so the description's brevity is acceptable. However, it does not explain what the list contains beyond 'financial symbols' (e.g., whether it includes ETFs, delisted companies, or specific exchanges), nor the expected output structure. Given the absence of an output schema and annotations, a bit more context would improve completeness.

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 tool has zero parameters and the input schema is empty, so there are no parameter semantics to explain. The description reasonably omits any parameter discussion, and the baseline score of 4 is appropriate because the schema fully covers the (nonexistent) parameters without requiring compensation.

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 retrieves a comprehensive list of financial symbols via the FMP Company Symbols List API, using specific verbs like 'retrieve' and naming the resource. It is unambiguous about its core function, though it does not explicitly differentiate from sibling list tools like getETFList or getCryptocurrencyList, relying on the name 'CompanySymbols' to imply equities focus.

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 gives a vague use case ('helping you explore the full range of available securities') but provides no explicit when-to-use or when-not-to-use guidance, no alternatives, and no exclusions. Sibling tools like getActivelyTradingList, getETFList, and getForexList exist, but the description does not clarify how this tool fits among them.

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