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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. The description still earns credit by defining stats.readers precisely (cumulative readers of the person page, re-reads excluded) and by specifying that works are returned in year order and that an absent slug yields null — behavior not present in the annotations.

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?

Front-loads the returned fields, then the input source, then the null case — a sensible ordering with no filler. It is one densely packed sentence-chain, which is slightly harder to scan than a bulleted enumeration would be, but every clause carries information.

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 no output schema present, the description fully assumes the burden of describing the response payload (identity, credits, sources, trivia, readership stats). Combined with input sourcing and the null case, an agent has everything needed to call this single-entity fetch 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 coverage is 0%, so the description carries the full burden for the single `slug` parameter. It compensates well by naming the two sibling tools that produce valid slugs and by defining the null behavior when no slug exists, which is meaning the bare `type: string, minLength: 1` schema cannot convey.

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 (returns) and resource (one person/creator), then enumerates exactly what comes back: name/aliases, works with roles in year order, sources, trivia, and stats.readers. An agent can distinguish it from list-oriented siblings like gamegene_games or gamegene_search without opening any 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?

Gives the prerequisite explicitly — the slug must come from gamegene_search or gamegene_game's credits — and states the null case for a missing slug. It does not spell out when *not* to use this tool versus other person-adjacent siblings, but the input-routing guidance is concrete enough to act on.

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