list_companies

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

No annotations exist, so the description carries the full behavioral burden. It does disclose the exact fields returned (ticker, name, tier, pub date, fiscal quarter range, series count), which is genuinely useful with no output schema. However, it says nothing about read-only nature, result volume/ordering, or pagination, so it only partially discharges that burden.

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?

A single sentence that front-loads the resource and then lists the returned fields with no filler. The trailing colon-list is slightly clunky but every clause carries information, so nothing is wasted.

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?

With zero parameters, no annotations, and no output schema, the only thing an agent needs is to know what it gets back, and the description supplies that field inventory. Minor omissions (ordering, total count) do not block correct invocation.

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 no parameter semantics to explain; baseline 4 applies. Schema description coverage is 100% and the input schema is an empty object, which is consistent with the description's no-argument framing.

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 the resource ('companies in the dataset') and enumerates the attributes returned, which distinguishes it from list_metrics and get_series. It stops short of an explicit verb ('list/return all companies') or any sibling comparison, so it is clear but not fully differentiated.

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?

Usage is only implied: by describing itself as the inventory of companies in the dataset, it suggests it is the discovery entry point. There is no explicit when-to-use, no condition favoring it over list_metrics, and no stated prerequisites or exclusions.

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