Build a content plan

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description adds substantial behavior beyond that: cadence caps on email and WhatsApp to avoid unsubscribes, campaign-phase assignment tied to the most important upcoming event, evergreen fallback on quiet days, and no-sales guidance on observances like Remembrance Day. These are real generation rules an agent could not infer from structured data.

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?

Four sentences, front-loaded with what is generated, then the awareness dimensions, then phase logic, then the return. Dense but every sentence carries information; the parenthetical phase list is long but useful enumeration.

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 12-parameter tool with no output schema, the description covers the generation logic and explicitly describes what comes back (slots to fill with captions and assets). Defaults for startDate/endDate/postsPerWeek/format are left entirely to the schema, which is acceptable given 83% coverage but a small 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 83%, so baseline is 3, but the description adds meaning: 'regions' drives event relevance ranking, 'platforms' interacts with cadence caps, and 'niche' shapes angles, hooks and shots. It does not clarify offer, format or postsPerWeek semantics beyond the schema, keeping it from a 5.

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?

Specific verb plus resource: 'Generate a day-by-day content calendar per platform for the coming weeks.' It is immediately distinguishable from siblings like event_calendar (event lookup) and asset_brief (asset creation) because it explicitly positions the output as slots to be filled later.

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?

Clear context: use it to plan posts across platforms, and the closing line 'Returns slots you then fill with captions and assets' routes the agent to a downstream tool. There are no explicit exclusions or named alternatives (e.g., when to prefer event_calendar first), so it stops short of a 5.

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