get_company_info

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered by structured data. The description adds the field inventory (sector, industry, employees, website, business summary), but that overlaps with the existing output schema and says nothing about latency, rate limits, or error behavior for invalid tickers.

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?

Front-loads the purpose in the first sentence and uses compact Args/Returns blocks with no filler. The Returns block is slightly redundant given the output schema exists, but the whole definition is short and well-organized.

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 single-parameter read tool with a full annotation safety profile and an output schema, the definition is close to sufficient. The decisive gap is namespace disambiguation from get_company_overview, plus no guidance on invalid-ticker behavior, which the sibling list and schema cannot supply.

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 description coverage is 0%, so the description carries the burden and does name the parameter's meaning ('ticker: Stock ticker symbol'). It stops there, giving no format example (e.g., 'AAPL'), exchange suffix handling, or case sensitivity, so compensation for the coverage gap is only minimal.

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?

States a specific verb and resource ('Get detailed company information and business description') and enumerates the content returned, so the agent knows what it fetches. However, it does not differentiate itself from the near-identical sibling 'get_company_overview' (nor from get_company_officers/get_fast_info), leaving real ambiguity in a crowded namespace.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives despite a sibling named get_company_overview that reads as a direct competitor. The agent must guess which company-detail tool to call.

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