Create an author

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

Adds substantial behavioral detail beyond annotations: is_ai_generated defaults to true and drives disclosure copy, changes are not public until a separate publish step, and a specific secret key scope is required. These details align with the annotations (readOnlyHint false, openWorldHint true) without contradiction.

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 concise yet information-dense. Every sentence serves a clear purpose: stating the operation, explaining the key flag, clarifying the mutation and non-publication behavior, and specifying the auth requirement. No redundant content.

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?

For a create operation with no output schema, the description covers all critical operational aspects: purpose, the most nuanced parameter (is_ai_generated), side effects on the customer's Site, the separation of publishing, and required credentials. An agent has enough to invoke it 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?

The input schema has only 40% parameter description coverage. The description compensates by deeply explaining is_ai_generated (persona vs real person, default true, disclosure implications). Bio and avatar_url already have schema descriptions, and name/is_default are self-explanatory, so the description adds value where needed.

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 opens with a clear, specific verb+resource: 'Create an author.' It also differentiates from sibling create tools (e.g., create_article, create_category) by naming the resource and noting it changes content on the customer's Site, confirming it is a write operation for authors.

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?

Provides explicit context for when to set is_ai_generated, states that publishing is a separate call, and specifies the required auth scope (wv_sk_ with authors:write). However, it does not explicitly contrast with update_author or delete_author to say 'use this when creating, not updating.'

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