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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and open-world behavior are covered. The description adds the useful scoping note that results are limited to companies featured in Fortune rankings, but says nothing about pagination behavior or result ordering beyond what the schema ('30 companies per page') already states.

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 tight sentences, front-loaded with the core action and resource, followed by the scoping and workflow hint. No filler.

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?

With annotations covering the safety profile and an output schema covering the return shape, the description only needs to establish purpose and scope, which it does. A brief note on pagination or the need to resolve filter slugs via fortune_company_filters would have made it fully self-sufficient.

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 100% across all 10 parameters, so the schema already documents paging, year, search, country, ranking, industry, and revenue/employee bounds. The description adds only 'by company name or query,' which marginally exceeds the schema. Baseline 3 is appropriate when the schema does the heavy lifting.

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 (Search) and resource (Fortune's public company directory), and explicitly positions itself against the sibling fortune_company by saying it is used to find a listing 'before requesting its profile.' An agent can distinguish this search tool from the profile tool without reading either schema.

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?

Gives clear context: use it to locate a company listing before pulling a profile, and scopes it to companies featured in Fortune rankings. It does not spell out when-not to use it or name fortune_company_filters as the required companion for filter values, though the schema covers that.

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