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 behavioral traits. It mentions the tool 'schedules' posts (a write operation) and gives some usage prompts, but does not disclose side effects, authentication needs, error handling, or idempotency. Adequate but could be more transparent.

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 concise (3 sentences) and front-loaded with the purpose. Could be slightly more structured (e.g., bullet points for platform-specific rules), but no extraneous information.

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's complexity (multi-platform, nested array with 8+ properties, no output schema, no annotations), the description is incomplete. It covers only core fields and carousel constraints, missing details on title, asset_id, media_url, platform_settings, return values, and error states.

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 adds value by explaining the need for platform, post_type, caption, scheduled_at and carousel item constraints (2-10). However, it omits explanations for title, asset_id, media_url, and platform_settings, leaving gaps.

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 clips or media on social platforms, with a specific verb (schedule) and resource (post). It distinguishes from siblings like list_scheduled_posts and cancel_scheduled_post.

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 advises asking the user for missing fields (platform, post_type, caption, scheduled_at) and gives platform-specific requirements, but does not explicitly state when to use this tool over alternatives (e.g., clip_video) nor provide exclusions.

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