get_company_info

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

With no annotations supplied, the description carries the full burden of behavioral disclosure. It only restates that the tool fetches info, without mentioning output format, data sources, potential errors, or the read-only nature beyond what is obvious from the verb.

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 a single short sentence with no filler, making it easy to scan. However, it is so brief that it borders on under-specification, which slightly detracts from the conciseness advantage.

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 lack of annotations and absence of an output schema, the description fails to communicate what 'basic company info' includes or what the response will look like. It also omits parameter semantics, leaving the agent under-informed for a tool that has only one parameter.

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?

The schema has one required parameter, 'symbol', with 0% description coverage. The description does not explain what 'symbol' refers to (e.g., ticker format, exchange, case sensitivity) or any constraints, so it adds no meaning beyond the parameter name.

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 uses a specific verb 'Fetch' and names the resource 'company info', which distinguishes it from sibling tools that handle stock price, historical data, news, or indices. However, 'basic company info' is vague about what exactly is included.

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 about when to use this tool versus alternatives like get_stock_price or get_stock_news. There are no exclusions or contextual hints, leaving the agent to infer usage from the tool name alone.

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