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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety and reach profile is covered. The description adds that the profile is 'public' and includes recent articles, but discloses nothing about pagination, how many recent articles appear, or rate/auth behavior. Adequate but not rich.

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, zero filler. What is returned is front-loaded and the disambiguation clause is placed last as a routing note.

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 the description need not explain return values, and the one required parameter is fully documented. The main residual gap is that it doesn't say how a contributor URL is obtained (e.g., from vanityfair_article output), which would complete the workflow for an agent starting cold.

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% and the single `url` parameter is already documented as 'Canonical Vanity Fair contributor URL'. The description adds no format, example, or resolution guidance beyond the schema, 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+resource ('Fetch one Vanity Fair contributor's public profile') and enumerates exactly what it returns (name, job title, biography, headshot, social links, recent articles). It also names the sibling vanityfair_article, so an agent can separate author lookups from article lookups 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 a contributor profile, use vanityfair_article for one story's content. That names a concrete alternative and the condition selecting it, though it doesn't cover the sibling tools vanityfair_news / vanityfair_headlines / vanityfair_sections.

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