company_overview

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

The annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful context about the sources (company site and LinkedIn) and the narrative format, but it does not disclose output shape, potential source bias, or limitations. No contradiction with annotations.

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 one tight, front-loaded sentence with no filler. Every clause adds meaning: what it produces, what it contains, and where the information comes from.

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 description covers the tool's purpose and sources, and annotations cover read-only/open-world behavior. However, with no output schema and nested optional parameters, an agent is left to infer the return shape and how fields like sector, country, and listed should be used together. It is adequate for a simple read-only overview but not fully 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 description coverage is 0% for the top-level context parameter, and the description does not explain any of the nested fields such as company, companyDomain, country, listed, sector, or date. The required company field is inferable from the tool name, but the description does not compensate for the low schema coverage.

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 a specific verb ('Produces') and a concrete deliverable ('narrative business overview') with content details (what the company does, products/services, target market) and sources. However, it does not explicitly distinguish itself from the sibling company_profile tool, so it falls short of a 5.

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 given about when to use this tool versus alternatives like company_profile, industry_overview, or market_size. The source qualifier is informative, but it does not tell an agent when to choose this tool or when to avoid it.

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