schedule_post

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

No annotations are present, so the description carries the full burden. It warns about common ID misuse and provider-specific constraints, but does not explicitly describe side effects (e.g., that this creates a scheduled post) or error/result behavior. It could be more transparent about what happens on success/failure.

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 well-structured with clear bullet points and an IMPORTANT section. It is somewhat lengthy but each sentence adds necessary guidance. The organization makes it easy to scan while covering multiple edge cases.

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 input schema and existence of an output schema, the description covers essential pre-requisites, provider nuances, and required formats. It does not need to explain return values since an output schema exists. It is sufficiently complete for an AI agent to invoke correctly.

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 meaningful context for page_id (external vs internal), provider (providerId for sub-account-less providers), planned_at (future UTC ISO8601), and image_posts (required for Instagram). However, it does not explain text, tiktok_params, or twitter_params, leaving 4 of 7 parameters partially or entirely undocumented.

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 on a single social network via Plus Tard and lists all supported providers. It distinguishes itself from sibling tools by specifying when to use it (for scheduling content) rather than validation, account listing, or registration.

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?

Provides explicit when-to-use guidance ('quand l'utilisateur veut programmer, publier ou scheduler') and detailed operational instructions: one call per network, prerequisite calls to list_accounts/get_user, correct page_id vs internal ID, provider-specific handling, Instagram image requirement, and UTC date format. This is exemplary.

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