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

Annotations cover the safety profile (readOnlyHint, openWorldHint), and the description adds meaningful context beyond that: the source's client-side 'load more' control is not followed, so the article list returned is only the initial batch. That is a real behavioral limitation an agent would otherwise discover only by inspecting results. It stops short of describing return format, but the output schema covers that.

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?

Three tight sentences: purpose and identifiers first, then the pagination caveat, then the alternative tool. Every sentence earns its place and nothing is redundant.

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 no explanation. The description covers purpose, both input paths, the pagination limitation, and the sibling alternative — everything an agent needs to select and invoke this tool correctly.

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 parameters (url and slug) are already documented in the schema with usage hints, including that url is an alternative to slug. The description mirrors this ('by slug or canonical url') without adding format or precedence detail, so the baseline 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?

States a specific verb (fetch) and resource (Foreign Policy contributor profile plus initial recent-article list), and specifies the two identifiers accepted (slug or canonical url). It also names the sibling it is not (foreignpolicy_article), so an agent can distinguish it 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?

Explicitly routes the agent: use this for an author profile plus their article list, and use foreignpolicy_article for a single story. The when-to-use condition is clear, though it gives no explicit when-not-to-use beyond the single named alternative.

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