yahoo_finance_ticker_holders

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

Discloses it returns four holder module types, but no annotations exist to offload safety/read-only status. Does not mention data freshness, rate limits, or result structure beyond module names.

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 main purpose. No redundant or extraneous words.

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 simple retrieval tool with one parameter and no output schema, the description covers the basics. It lacks detail on the structure of the returned modules, but that is acceptable given the tool's simplicity.

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 has 100% coverage for the single symbol parameter, and the description adds that it returns holders for that symbol. Baseline of 3 is appropriate as no additional parameter nuance is provided beyond the 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 clearly states it returns holder modules for a symbol. The verb 'returns' plus the specific data types distinguish it from sibling tools like yahoo_finance_ticker_info.

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 implies usage when holder information is needed, but does not explicitly say when to use vs. alternatives like yahoo_finance_ticker_analysts or yahoo_finance_ticker_earnings.

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