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

Annotations already cover the safety profile (readOnly=false, idempotent=true, destructive=false). The description adds genuine behavioral context beyond them: slots are stored as local wall-clock in the workspace timezone and remain stable across DST, which an agent would otherwise get wrong.

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?

Front-loaded purpose, then two focused sentences on the tricky parameter semantics. The trailing 'Related:' list is slightly tacked-on but short and useful; overall well-sized with little waste.

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?

With an output schema present there is no need to describe returns, and annotations cover safety. The description covers purpose, both indexed params' semantics, and the timezone subtlety; only explicit usage routing is thin, which is a minor gap.

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 coverage is 100%, so baseline would be 3, but the schema leaves weekday's meaning undocumented (only min/max 1-7). The description supplies the 1=Monday…7=Sunday mapping and reinforces the 24-hour local-wall-clock semantics of the time value, adding real value over the 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 states a specific verb pair (adds/removes), the exact resource (recurring weekday+time posting slots), and the target (channel). It clearly distinguishes itself from siblings like reschedule_post (single post) and update_channel_settings (channel-level config).

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?

It lists related tools (list_channels, get_calendar, get_channel_rules) which implies where slot ids come from, but never states explicit when-to-use vs when-not conditions or which related tool to call first. Usage is inferable rather than stated.

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