create_publication

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

With no annotations, the description covers key behavioral traits: all 9 langs required, cover_path must be absolute JPEG path, and default values for archived and is_complete. It does not mention error handling or duplicate checks, but the provided details are solid.

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 moderately concise, but the bullet-like args section adds clarity. The key requirement (all 9 langs) is front-loaded. Minor verbosity from listing all args could be tightened.

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?

Given 9 parameters, 7 required, no annotations, and an output schema, the description covers essential constraints and types. It explains non-obvious requirements (e.g., all 9 langs) but could mention validation or side effects for fuller completeness.

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 fully compensates. It explains each parameter's purpose and constraints, e.g., headers/descriptions require all 9 langs, cover_path is an absolute path, copyright_terms lists examples, and default values are noted.

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 'Create a new publication on cwbe' with a specific verb and resource. It further clarifies constraints like requiring all 9 languages, which distinguishes it from sibling tools like delete_publication or update_publication_flags.

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?

The description does not explicitly state when to use this tool versus alternatives. It implies usage by detailing required parameters, but lacks guidance on when not to use it or how to decide between create and update tools.

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