get_stock_metadata

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

With no annotations present, the description bears full responsibility for behavioral disclosure. It only states 'Get metadata' without confirming safety (read-only), describing error behavior for invalid tickers, or mentioning rate limits. This leaves the agent with insufficient behavioral 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?

The description is concise, using two sentences and an args block. It is front-loaded with the purpose and specific fields. No redundant information is present.

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?

The tool has an output schema, so the description is not required to list all return fields. However, it only mentions a few fields (name, exchange, description, date range). For a metadata tool, the full output may include additional fields like currency, sector, etc. The description covers basics but could be more 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 0%, so the description must fully define the parameter. It does so clearly: 'ticker: Stock ticker symbol (e.g. AAPL, MSFT, GOOGL).' This provides both the parameter's meaning and examples, enabling correct usage.

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 retrieves metadata for a stock ticker and lists specific fields (name, exchange, description, date range). However, it does not differentiate from sibling tools like get_company_meta or get_fundamentals_definitions, which likely serve similar purposes.

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 on when to use this tool versus alternatives. The description lacks context on prerequisites, such as needing a valid ticker, or scenarios where other tools (e.g., get_fundamentals_definitions) might be more appropriate.

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