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 usefully adds the shape of the returned profile (name, bio, recent articles), but discloses nothing about pagination, auth, or how many articles are included.

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 that states the resource first and its contents second, with no filler. It is efficient, though very short for a tool with two undocumented parameters.

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?

An output schema exists, so return values need not be spelled out. However, for a two-parameter tool with 0% schema coverage and no required fields, the description should clarify how 'url' and 'slug' are used and how they relate; that gap keeps it only adequate.

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 both 'url' and 'slug', and the description never explains what either parameter is or which one to supply. The phrase 'contributor page' faintly hints that 'url' points at that page, but this is left to inference and 'slug' is entirely unexplained.

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 Foreign Affairs contributor's public profile) and enumerates its contents (name, bio, recent articles), which is far more concrete than the bare tool name. It reads distinctly from siblings like foreignaffairs_article or foreignaffairs_headlines, though it doesn't explicitly contrast itself with them.

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 guidance on when to use this tool versus the article, headlines, or topic siblings, and no mention of prerequisites. The agent must infer usage purely from the noun phrase.

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