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

No annotations are provided, so the description carries the full behavioral burden, yet it discloses almost nothing. It does not say whether the parent calendar must already exist, whether the row is immediately visible or silent, what the mandatory calendar_id implies, or what is returned (and there is no output schema to fill that gap). Only "draft" conveys any state information.

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 single sentence is front-loaded and contains no filler. However, for a 12-parameter mutation tool it is far too thin to earn its place as the only guidance, so brevity here reads as under-specification rather than economy.

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?

A 12-parameter create operation with no annotations, no output schema, and sparse schema descriptions needs substantially more explanation than one sentence. Nothing tells the agent about required context, defaults, side effects, or return behavior.

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?

Twelve parameters with only 25% schema description coverage, and the description mentions no parameters at all. Fields like post_type, target_platform, target_account_id, scheduled_at, linked_asset_id, and hashtags are left entirely unexplained in both places, so the description fails to compensate for the coverage gap.

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?

"Add a draft row to a content calendar" names a verb and a resource, and the word "draft" hints at the pre-scheduling state. But it never distinguishes this from update_calendar_row, schedule_calendar_row, or delete_calendar_row, so an agent must infer which one to pick from the name alone.

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?

There is no statement of when to use this tool versus alternatives. Siblings such as update_calendar_row, schedule_calendar_row, and create_content_calendar are all adjacent operations, and the description offers no routing guidance between them.

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