schedule_post

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

The description discloses only that it supports auto_adapt threading. With no annotations, there is no information about side effects, permission requirements, or what happens upon creation, so the agent is left unaware of critical behavioral traits.

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 brief, which is concise in word count but severely under-specified for a tool with 8 parameters and nested objects. It lacks the structure needed to convey essential information, making it an underspecification rather than true conciseness.

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 the tool has no annotations, no output schema, and 8 parameters, the one-sentence description is grossly incomplete. It does not explain return values, usage context, or parameter relationships, so the agent cannot reliably invoke the tool.

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 0%, and the description offers no explanation for parameters such as account_ids, text, scheduled_at, or state. The only hint is for auto_adapt, but even that is vague, leaving most parameters semantically unclear.

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 creates a scheduled post, which is a specific action. However, it does not explicitly distinguish itself from sibling tools like schedule_posts_bulk or publish_post_now, relying mostly on the tool name for differentiation.

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 is provided on when to use this tool versus alternatives. The description implies scheduling but does not mention scenarios like bulk scheduling or immediate publishing, leaving the agent without decision criteria.

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