Create article

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

With no annotations, the description carries the burden and is effective. It discloses that content is World Anvil BBCode with examples and that new articles default to private+draft, with a way to publish immediately. It does not cover auth or return values, but the core creation behavior is transparent.

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 two sentences with no filler. The first states the action, the second packs content format and default behavior, making it efficient and front-loaded.

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 and no annotations or output schema, the description covers the main behavior, content format, and visibility defaults. It leaves advanced params like extra_fields and template_type to the schema, which is acceptable, though return behavior is not mentioned.

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 high at 78%, so the baseline is near 3, but the description adds value by combining state='public' and is_draft=false for immediate publishing and showing BBCode examples. This supplements the schema without redundant repetition.

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 clearly states 'Create a new article in a world,' specifying the verb, resource, and scope. It distinguishes from siblings by emphasizing 'new' and touches on content format, making it stand apart from update/delete tools.

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?

It provides clear context by noting articles default to private+draft and gives instructions to publish immediately. However, it does not explicitly mention when to use a specific alternative like update_article, though the 'new' wording makes this implicit.

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