create_content

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

With no annotations, the description carries full burden for behavioral disclosure, but it only states 'Creates any content type'. It does not disclose the mutation side effects, authentication requirements (token/cookie), validation behavior, or response format. This is a significant gap for a creation 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 a single sentence, which is concise in length, but it is under-specified rather than effectively concise. It does not provide enough information to be useful, and the brevity is not a virtue given the tool's complexity.

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?

The tool has 5 parameters, a nested data object, and no annotations or output schema. The description provides almost no context about how to structure requests, what data format is expected, or what happens after creation. It is completely inadequate for an agent 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?

The schema coverage is 0%, and the description adds no meaning to the parameters. It mentions 'content_type' indirectly but does not explain the 'data' object, 'api_url', or auth credentials. The description fails entirely to compensate for the lack of parameter documentation.

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 the primary action ('Creates') and the resource ('any content type in Plone'). It differentiates from sibling tools like patch_content (update) and delete_content (delete), but the scope of 'any content type' is broad and not precise about which content types are supported.

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. There are sibling creation tools like create_dynamic_page_row and create_dynamic_page_row_featured, and the description does not explain when to choose create_content over them or mention any prerequisites or context.

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