Publish or unpublish content

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

With no annotations provided, the description carries the full burden and does convey the core behavior: flipping the published flag and optionally scheduling a future publish. It also discloses the table restriction for publish_at. It does not mention response shape, permissions, or side effects like content becoming immediately public, but for a simple state toggle this is a moderate disclosure.

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 two concise sentences with no filler. The primary action is front-loaded, and the important publish_at constraint is included compactly in the second sentence.

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 description covers the main invocation semantics for a relatively simple tool, and the input schema supplies the required parameters. However, there is no output schema and no mention of what the tool returns or whether scheduled publishing requires published to be true, leaving some behavior to inference.

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 25%, but the description adds meaning by mapping 'table' to blog posts, case studies, and resources, clarifying that 'published' is a flag to toggle, and explaining that publish_at is for scheduled publishing on blog_posts and case_studies only. The slug parameter is left to inference, but its role is fairly obvious.

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 uses a specific verb and resource: 'Toggle the published flag on a blog post, case study, or resource.' This clearly distinguishes it from generic tools like update_content and destructive tools like delete_content. The title reinforces the publish/unpublish purpose.

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 the tool: whenever the published state of content needs to change or a scheduled publish is needed. However, it does not explicitly compare against update_content or state when not to use it, leaving the agent to infer the specialization.

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