wordpress_schedule_post

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

With no annotations, the description carries full burden for safety and behavior. It only mentions scheduling and date format, but doesn't disclose whether the post must already be in a draft state, if existing schedules are overwritten, permission requirements, or what happens on success/failure. For a mutation tool, this is a significant gap.

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, consisting of one sentence plus a date format note. Every word contributes to the core purpose and the most essential usage detail.

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 is simple but the description omits critical context like timezone handling, whether the datetime must be strictly in the future, return value, and relationship to publish_post. Given no output schema and no annotations, the description is not complete enough for an agent to invoke correctly without guessing.

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 description adds the date format for the datetime parameter, which is valuable since the schema has no descriptions. However, postId is left entirely to inference from its name, and there's no clarification of timezone or accepted ranges. Partial compensation for 0% 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 clearly states the tool schedules a post for future publication, using the specific verb 'Schedule' and resource 'post'. The phrase 'future publication' implies distinction from immediate publishing, though it doesn't explicitly name sibling alternatives.

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 on when to use this tool versus alternatives like wordpress_publish_post or wordpress_schedule_event. The date format hint is helpful but doesn't explain context, prerequisites, or exclusions.

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