publer_preview_schedule_post

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

No annotations are provided, so the description must fully disclose behavior. It does not mention what validation entails, return value, idempotency, authentication needs, or any side effects. The agent gets minimal guidance on behavior.

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 with no fluff, but it is under-informative. While concise, it sacrifices necessary detail, earning a 4 rather than 5.

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 7 parameters (0 required), no output schema, and nested objects. The description does not mention return values, how validation results are communicated, or how to construct the payload. Incomplete for an agent to use effectively.

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 14% (only scheduledAt has a description). The tool description adds no parameter details. With 7 parameters and 0 required, the description provides no semantic help beyond the schema, which is sparse.

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 specific verbs 'Build and validate' and identifies the resource 'Publer schedule payload'. It clearly distinguishes from the sibling publer_schedule_post by stating it does not call write endpoints.

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 testing before actual scheduling ('without calling Publer write endpoints'), but lacks explicit when-to-use, when-not-to-use, or alternative tools. Sibling publer_schedule_post is the likely alternative but not named.

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