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

With no annotations, the description must carry the behavioral burden. It discloses that results are ranked by coverage count, giving a sense of ordering, but it does not mention sorting direction, scope of the corpus, rate limits, or any side effects.

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 an eight-word sentence with no filler. It front-loads the resource ('extracted entities') and packs the ranking criterion into the same 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 one-parameter read tool the description gives the gist, but it omits the meaning of 'coverage count', how limit behaves, and what the return shape looks like (no output schema). With a sibling list like related_stories, an agent cannot confidently choose this tool based solely on the description.

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 schema has zero property descriptions and the description does not mention the 'limit' parameter at all. The parameter's name and min/max constraints imply it caps the number of returned topics, but the description fails to compensate for the missing schema coverage.

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 states a concrete output: extracted entities (companies, models, people, themes) ranked by coverage count. It identifies the resource and ordering, though it doesn't explicitly differentiate from sibling tools like related_stories or search_news.

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 guidance is provided about when to call list_topics versus the sibling tools. There are no exclusions, prerequisites, or alternative tool references.

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