Create content

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

With no annotations, the description carries the behavioral burden. It discloses that the fields object must match table columns and gives column lists plus the type enum for resources. However, it doesn't mention success/error behavior, required-vs-optional fields, or what is returned after creation.

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 purpose is front-loaded and the column lists are dense but efficient. The only minor issue is that long inline lists are slightly harder to scan, though every piece of information earns its place.

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 three content types, nested objects, no output schema, and no annotations, the description is incomplete. It omits required-field constraints, data types for most columns, and any mention of return values or validation behavior, so an agent could construct an invalid fields object.

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 only defines fields as 'Column values for the new row,' so the description adds essential semantics by enumerating exact columns per table, including the nested metrics structure and the type enum for resources. This compensates 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?

Description opens with a specific verb and resource: 'Create a new blog post, case study, or resource.' This clearly distinguishes it from update/delete/set-published siblings and even excludes job postings, which have their own create tool.

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 gives clear context for when to use it: creating new content rows. Enumerating only blog_posts, case_studies, and resources routes agents away from sibling tools like create_job_posting, though it never explicitly names update_content as the alternative for existing rows.

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