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

Annotations already declare readOnlyHint and idempotentHint, so the safety profile is covered. The description adds meaningful behavioral context: 'resolved' indicates identity resolution, 'deduplicated observed audience footprint' signals data processing, and the caveat 'not guaranteed to be a complete bibliography' sets expectations about data completeness. No contradiction with 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?

The description is a single front-loaded sentence of about 20 words. It leads with the primary output, lists additional return components, and ends with an important data-quality caveat. No filler or redundancy.

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?

This is a simple tool with one required integer parameter, a rich output schema, and annotations covering read-only and idempotent behavior. The description names the full return set and flags a data limitation. It is slightly incomplete on how to obtain or interpret identity_id, but for a straightforward retrieval tool that is a minor gap.

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%, so the description must compensate. It connects identity_id to a 'Scrykeeper author identity' and a 'resolved' status, adding domain context. However, it does not explain where identity_id comes from, its format, or how resolution works, leaving the agent with only the parameter name and a scant hint.

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 states a specific verb and resource: 'Get a resolved Scrykeeper author identity, known works and deduplicated observed audience footprint.' This clearly indicates an author-intelligence retrieval tool. However, it does not explicitly contrast with siblings like search_market or get_story, relying on the tool name for differentiation.

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?

No guidance is given on when to use this tool versus the sibling tools. There are no mentions of alternatives, exclusions, prerequisites, or the source of identity_id. Usage is only loosely implied by the purpose, without any decision support.

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