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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real behavioral value beyond that: it clarifies these are unscheduled ideas paired with a boolean-like 'already on the posting calendar' signal, which shapes how the agent should interpret results. Pagination behavior beyond the limit parameter and permissions are unstated.

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 core identification is front-loaded in the first clause, and the disambiguation follows in the second. The em-dash content list is long but each item conveys what a record contains, so it earns its space. Slight trimming of the item enumeration would tighten it further.

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 six parameters, no output schema, and a read-only list operation, the description does the needed work by describing the shape of returned records (date, hook, copy starter, calendar status). The main gap is unexplained status filter values, which is the one thing an agent could get wrong when invoking it.

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 83%, so the schema already documents from, to, limit and site_id. The description's 'Dates are YYYY-MM-DD' and 'suggested date' wording reinforces the range semantics, which is mild added value. The status enum (planned/in_progress/published/skipped) has no description in either the schema or the description, leaving the filter's meaning to inference.

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 names a specific resource (the marketing hub's dated content ideas) and enumerates what each record carries: suggested date, seasonal hook, copy starter, and calendar status. It explicitly separates itself from schedule_social_post and get_calendar. It does not differentiate from the nearby sibling list_marketing_ideas, which is the one remaining ambiguity.

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 gives an explicit routing rule: 'These are ideas, not scheduled posts; to schedule one use schedule_social_post, and get_calendar reads what is actually scheduled.' That tells the agent both the alternative tools and the condition that selects them. No guidance is offered for choosing between this and list_marketing_ideas.

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