createArticle

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

With no annotations, the description bears full responsibility for behavioral disclosure. It only states 'Create', implying mutation, but does not describe side effects, required permissions, or what happens on success or failure. More detail is needed for a mutation tool.

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 only five words, which is excessively brief. While concise, it sacrifices crucial information and is not structured to be helpful. Every sentence must earn its place, and this one does not add value beyond the tool name.

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 tool's complexity (8 parameters, 3 required, nested objects, a default value, no output schema), the description is woefully incomplete. It fails to explain the purpose of parameters, return values, or behavior, leaving the agent with insufficient context to use the tool 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?

Schema description coverage is only 13% (only blogId has a description). The tool description adds no additional meaning to the seven other parameters, such as title, content, tags, or the nested image object. This is insufficient compensation for the low schema coverage.

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 'Create a blog article' clearly identifies the action and resource, matching the tool name. However, it does not distinguish this tool from its many sibling create tools (e.g., createProduct, createPage), and the description adds little beyond the name itself.

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?

No guidance is provided on when to use this tool versus alternatives like createPage or other blog-related tools. There is no mention of prerequisites (e.g., needing a blog ID) or exclusions.

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