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 discloses defaults, optional metrics projection, identity/source lineage preservation, per-entry errors for unknown tickers, and the lack of historical point-in-time filtering—all beyond what the schema states.

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 three sentences with no wasted words. The primary purpose is front-loaded, and each subsequent sentence adds meaningful behavioral detail without repeating schema content.

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?

Despite having no output schema, the description provides a solid picture of expected behavior: batch scope, defaults, per-entry errors, and identity/lineage preservation. It does not specify the exact response structure or error format, but for a read-oriented batch tool this is reasonably complete.

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 coverage is 100%, so the baseline is 3. The description adds useful behavioral nuance: periods default to 'one newest period per issuer,' metrics are framed as an 'optional projection,' and tickers are explicitly 1–20 comma-separated. This clarifies parameter behavior beyond the raw schema.

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 specific verb and resource: 'Read annual fundamentals' with explicit batch scope '1–20 comma-separated ticker symbols in one request.' It clearly differentiates itself from the sibling get_fundamentals by emphasizing the multi-ticker batch capability.

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 makes it clear this tool is for reading fundamentals for multiple tickers in one request. It also provides an exclusion by stating 'No historical point-in-time filtering,' implying a different tool is needed for historical data, though it does not name that alternative explicitly.

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