Get Company Overview Tool

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

With no annotations, the description carries the behavioral burden. It clearly discloses the output scope, including that the business description is truncated. For a read-only overview tool, this is adequate, though it does not mention error or empty-data handling.

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 concise sentences: the first states the action, the second enumerates the return fields. No filler, no repetition, and the main purpose is front-loaded.

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?

Given the tool's low complexity, one required parameter, and the presence of an output schema, the description is largely complete. It could add how unavailable fields are returned, but the listed fields and truncation caveat cover most of what an agent needs.

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%, and the ticker description already provides a format example and search_ticker fallback guidance. The tool description adds no new parameter semantics beyond reusing 'ticker symbol'.

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 ('Get a company profile overview for a ticker symbol') and enumerates the returned fields, making its domain distinct from siblings like get_stock_quote_tool or get_financial_ratios_tool. It doesn't explicitly name a sibling, but the field list is sufficient for differentiation.

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 schema's ticker description gives an explicit conditional routing rule: if only a company name is available, call search_ticker first. This covers the main identification ambiguity, though it does not state when to prefer this tool over the other financial siblings.

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