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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds that the profile is public, implying no authentication, and specifies the categories of data returned; it does not address rate limits, pagination, or response structure, so it adds only moderate context beyond 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?

A single front-loaded sentence identifies the resource and then lists its components without any filler. Every clause adds informative content and nothing is repeated from the structured fields.

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 tool is a simple read-only detail endpoint with an output schema, annotations, and fully documented parameters, so the description does not need to explain return values. It provides a useful content overview but omits that at least one of url or slug must be supplied — an important operational detail given that neither parameter is marked required.

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%, so both slug and url are fully documented in the schema. The description does not mention either parameter or explain how to choose between them; with full schema coverage, the baseline of 3 is appropriate.

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 identifies the resource — one company's public Fortune profile — and enumerates the exact content types it returns (fact sheet, rankings, workplace tables, earnings links, social accounts). It lacks an explicit verb and does not name sibling tools such as fortune_companies or fortune_company_filters, so it stops short of full 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?

There is no explicit when-to-use guidance or mention of alternatives. The content list implies the tool is for retrieving a single company's detailed profile, but an agent must infer that it should be used instead of fortune_companies for list/search tasks or fortune_company_filters for filtering.

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