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 the nature of the payload (real-time wealth, wealth history, list appearances), which is useful context, but it discloses nothing about auth requirements, rate limits, or freshness guarantees, and an output schema already documents the return shape.

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 with no wasted words; the resource is stated first and the enrichment details follow. Slightly verbose in its field enumeration but appropriately sized.

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?

Because an output schema exists, return values need not be explained, and the annotations cover the safety profile. However, for a required URI argument with zero schema documentation, the description should specify what form that URI takes, which it does not.

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 single parameter 'uri' has 0% schema description coverage, so the description carries full responsibility. It only weakly hints at the parameter's meaning via 'from the public profile page', leaving the required URI format, expected value, and whether it must be a Forbes URL entirely unspecified.

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 names a specific resource (a Forbes person's public profile) and enumerates the returned content (biography, wealth, wealth history, personal facts, list appearances), so an agent knows what it fetches. It is clear but does not differentiate itself from sibling tools such as forbes_billionaires, forbes_author, or forbes_article.

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, no prerequisites, and no alternatives named. An agent must infer from the name alone that this is the tool for fetching a single notable person's Forbes profile rather than a list of billionaires or an author page.

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