Create Help Center Article

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

Annotations already indicate the tool is a mutation (readOnlyHint=false) and not destructive. The description adds that the locale becomes the source_locale, but this is also in the schema. No additional behavioral traits (e.g., side effects, rate limits) are disclosed beyond what annotations and schema provide.

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?

Two sentences with front-loaded purpose: 'Create a new article in a section and return the created article with its id.' Every sentence serves a purpose without 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?

With 11 parameters and no output schema, the description is minimal. It covers the return value ('with its id') and the key required parameter, but doesn't explain optional parameters like draft, promoted, etc. However, schema covers all parameters, so the description is adequate but not rich.

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 100%, so baseline is 3. The description only mentions 'permission_group_id' and 'locale' as source_locale, which repeats schema info. No new meaning is added beyond what the input schema already provides.

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 section and return the created article with its id.' It specifies the verb (create) and resource (article), and distinguishes from sibling 'create_article_translation' by noting that for other locales, that sibling should be used.

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 provides explicit guidance on the required 'permission_group_id' and how to find it using 'list_permission_groups'. It also directs to 'create_article_translation' for adding content in other locales, giving clear context on when to use this tool versus alternatives.

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