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 useful context by calling out that only public profiles are returned and by listing the content sections, but says nothing about failure modes, invalid/unknown URIs, or rate limits. Adequate but not rich beyond the structured fields.

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 sentences with zero filler; the payload description comes first and the sibling routing comes last. Every clause earns its place.

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-only fetch with an output schema that documents the return shape, the description covers the essentials: what it returns, that it is public, and how to obtain the input via the sibling. Nothing an agent needs to invoke it correctly is missing.

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?

There is a single parameter with 100% schema description coverage ('Forbes person URI'), so the schema already carries the meaning. The description references `uri` but adds no syntax, format, or provenance guidance (e.g., where to obtain the URI), so the baseline 3 applies.

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 (Fetch) plus the resource (a public Forbes person profile) and enumerates the payload it combines: biography, net-worth display, wealth history, personal facts, and list appearances. It also explicitly distinguishes itself from the discovery sibling forbes_billionaires, so an agent can route correctly without opening 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?

It names the alternative (forbes_billionaires) and its role (discover ranked profiles), which tells the agent this tool is the follow-up detail lookup keyed by a URI. It gives no explicit when-not conditions or note that the URI must originate from that discovery tool, so it falls just short of the 5 bar for complete routing guidance.

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