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

Annotations already declare readOnly, idempotent, and non-destructive, so safety is covered. The description does add genuine behavioral context (93-day max range, timezone-qualified timestamps, pagination), but it references 'nextOffset' while the actual schema field is 'offset' — a naming mismatch that can mislead an agent invoking the tool.

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 with the tool's purpose and kept to three tight sentences. The opening line slightly duplicates the title, but otherwise every sentence contributes concrete 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?

No output schema exists, but the description adequately characterizes the return (timezone-qualified scheduled items) and scoping. It falls short only on the limit parameter and the offset naming inconsistency, leaving minor gaps for a read-only tool.

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 0%, so the description carries full burden for 5 parameters. It conveys the date-range concept and alludes to content groups and offset paging, but never explains start/end format, the limit default/max, or the offset default — and it renames offset to 'nextOffset'.

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 clear verb+resource combination: read scheduled posts, videos, and stories aggregated into a publishing calendar. The 'across your owned content groups' scope meaningfully distinguishes it from the granular listPosts/listStories/listVideos siblings, though it never names those siblings explicitly.

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?

Only guidance offered is 'Use nextOffset to page through busy calendars', which implies usage for large result sets but doesn't say when to prefer this over siblings like listPosts or getGroupAnalytics. No when-not conditions or prerequisites are given.

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