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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds genuinely useful context beyond that: it discloses the returned profile fields (name, bio, contact email, social accounts 'where published') and that only one page of recent stories is included, which warns the agent about truncation. It stops short of describing pagination limits or rate/auth behavior.

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 dense sentence that front-loads the resource and then lists the payload. Nothing is wasted and no sentence fails to earn 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?

With an output schema present, return values need not be detailed, yet the description still summarizes them helpfully. Combined with annotations covering the read-only/open-world profile, an agent has what it needs to call the tool; only explicit usage guidance for the sibling tools 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?

Schema coverage is 100%, so both parameters are already documented in the schema. The description's phrase 'one page of their recent bylined stories' corroborates the page parameter's meaning but adds no syntax or constraint beyond what the schema states. Baseline 3 applies when the schema carries the load.

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 resource (one ProPublica staff/contributor's public profile) and enumerates its contents, so an agent knows exactly what it returns. It does not explicitly differentiate itself from the sibling propublica_article/headlines/news tools, but the author-profile scope is unambiguous from the name plus description.

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?

Usage is implied: fetch an author profile given a canonical propublica.org/people/<slug> URL. There is no explicit when-to-use/when-not guidance and no mention of alternatives such as searching for stories by that author instead of fetching the profile. Adequate but leaves routing to inference.

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