schedule

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

Discloses side effects: writes to YAML store, makes HTTP requests for immediate variants, requires credentials. States idempotent on (content.id, channel). No annotations provided, so description fully covers 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?

Description is concise (5 sentences), front-loaded with purpose and usage, no redundant information. Every sentence adds value.

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?

Covers purpose, usage, side effects, idempotency, and alternatives. Missing explanation of return value/output (no output schema), though complexity and sibling differentiation are well-handled.

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 33% (low), requiring description to compensate. However, description only mentions schedule_at in context, not other parameters like content, variants, profile_name. Insufficient addition beyond schema.

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 enqueues channel variants with schedule_at for future publishing and immediately publishes those without. It distinguishes from siblings: schedule for mixed timing, publish for all-immediate, drain for processing queue.

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?

Explicitly tells when to use this tool versus alternatives: schedule when any variant needs future time, publish for immediate, drain for processing. Also mentions prerequisites (credentials) and idempotency.

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