Create Help Center Article

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

The description notes that the locale becomes the source_locale, which is a behavioral trait not in annotations. However, it does not elaborate on other aspects like side effects (openWorldHint=true) or authorization details beyond the permission_group_id. Annotations already indicate readOnlyHint=false and destructiveHint=false, so no 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?

Two concise sentences with no redundant information. Every sentence provides essential guidance without extra fluff.

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 the complexity (11 parameters, no output schema), the description covers the core purpose and one key behavior but lacks details on return value or post-creation state. It is adequate for basic understanding but could be more helpful for invocation.

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?

With 55% schema description coverage, the description adds value by explaining permission_group_id usage and locale behavior, but many parameters (e.g., body, draft, label_names) have schema descriptions. The description does not deeply compensate for missing schema descriptions of all 11 parameters.

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 explicitly states 'Create a new article in a section.' This is a specific verb+resource pair that clearly distinguishes it from sibling tools like create_article_translation, update_article, etc.

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 advises using list_permission_groups to find the required permission_group_id and directs that adding content in other locales should use create_article_translation. It provides clear context for prerequisites and alternatives, though it could explicitly state when not to use this tool.

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