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

With no annotations, the description carries the burden, and it does disclose cardinality (exactly 10) and data provenance (SEC 10-K filings), which implies a static, read-only catalog. It omits whether identifiers returned are what get_signal expects, and gives no auth or freshness/caching context.

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?

One front-loaded sentence with every clause earning its place: the verb, the count, the domain, and the source. No filler.

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 parameterless discovery call with no output schema, the description should say what each listed item contains (theme name, id) so the agent knows it can chain into get_signal. That chaining affordance — the main thing this description needs to convey — is absent.

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 takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description correctly implies an unfiltered full listing.

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 ('List') and resource ('10 risk themes'), plus the corpus (SEC 10-K filings of 300+ S&P 500 companies), which is genuinely informative scope. It does not, however, reconcile 'themes' with the tool name 'signals' or distinguish itself from the sibling get_signal, which fetches a single item.

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?

No statement of when to use this vs get_signal or list_companies; the agent must infer that this is the entry-point enumeration and that get_signal retrieves detail. No prerequisites or exclusions are given.

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