wordpress_schedule_post

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

No annotations are provided, and the description only states the action (schedule post). It does not disclose prerequisites (e.g., post must exist and be in draft), side effects, or what happens if the datetime is in the past. Significant gaps remain.

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 extremely concise: one sentence plus a format note. It is front-loaded and contains no fluff, making it efficient for quick reading.

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?

For a tool with two required parameters and no output schema or annotations, the description is too sparse. It omits return values, error conditions, and prerequisites (e.g., post must exist and be draft). The agent lacks sufficient information to use it reliably.

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 0% schema description coverage, the description must compensate. It provides the datetime format but adds no explanation for postId (e.g., where to get it, that the post must exist). Half the parameters lack semantic context.

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 'Schedule a post for future publication' with a specific verb and resource, and provides the required date format. It distinguishes from siblings like wordpress_publish_post which publishes immediately.

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 implies use for scheduling future posts but does not provide explicit guidance on when not to use or alternatives like wordpress_publish_post. The date format hint is helpful but incomplete for context.

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