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

Annotations already declare this a read-only, idempotent, non-destructive, closed-world operation, so the safety profile is covered. The description adds substantive context beyond that: the data source behind a suggestion and its numeric threshold, and the fact that results are expressed in the workspace's time zone. It stops short of describing the return shape or what happens with an unrecognized platform slug.

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?

Three sentences, zero redundancy, with the core capability front-loaded and the basis logic and default-selection instruction following in priority order. Nothing could be cut without losing 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?

For a read-only four-parameter tool with no output schema, the description covers the source of the advice, its threshold, time-zone handling, and how to present results. The main remaining gap is the shape of the returned suggestions, which the description leaves implied rather than stated.

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 100%, documenting 'after' (earliest time, default now), 'count' (1-5, default 3), 'platforms' (slugs), and 'workspace_uid' (from list_workspaces). The description reinforces platform scope and time zone but adds no new parameter-level meaning beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource — 'Suggest good times to post on each platform' — plus the time-zone scope. No sibling tool recommends posting times, so the agent can confidently route here from create_post or get_post_analytics.

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?

Gives the decision rule for how the suggestions are derived (at least 10 published posts with engagement in the last 90 days triggers the analytics basis, otherwise general guidance) and instructs the agent to offer the first suggestion as the default. No explicit when-not-to-use clause or named alternative, but no sibling overlaps this function.

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