get_stock_info

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

No annotations exist, and description only implies a read operation via 'Get'. Does not disclose side effects, authentication needs, rate limits, or other behavioral traits.

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?

Two sentences with no wasted words. Front-loaded with main purpose, then adds constraints. Ideal length for a simple tool.

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?

Covers main fields returned and max codes, but lacks return format (though no output schema), error conditions, and prerequisites. Adequate for a low-complexity tool.

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?

Adds value with 'up to 400 codes' constraint beyond the schema. However, does not explain what the codes represent (e.g., stock tickers) or format expectations.

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?

Clearly states 'Get stock basic+snapshot info' and lists specific fields (name, lot size, market cap, PE). Suffers slightly from lack of explicit differentiation from siblings like get_company_profile or get_snapshot, but the mention of underlying tool helps.

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 on when to use this tool vs the many sibling tools. Only mentions a max of 400 codes and an underlying tool, but no context for selection.

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