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

With no annotations, the description carries the full burden, and it does disclose one genuinely non-obvious trait: queued Nova posts are not cancelled by row removal. However, it says nothing about whether generated assets are also removed, whether the action is reversible, what permissions are needed, or how many rows can be deleted per call.

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?

A single front-loaded sentence with zero filler, and the scoping caveat is tucked into a parenthetical rather than burying the main verb. It is arguably too terse for a multi-parameter mutation, but nothing in it is wasted.

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 destructive, three-parameter mutation with no annotations, no output schema, and low parameter coverage, the description does the minimum: it clarifies the Nova-queue side effect but omits return behavior, partial-failure semantics, cascading asset deletion, and permission requirements.

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 only 33% — calendar_id and row_ids have no schema descriptions, and the description only obliquely implies them ("multiple post rows", "content calendar"). Constraints such as whether all row_ids must belong to calendar_id, ordering, or maximum batch size are undocumented anywhere.

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 ("Remove multiple post rows from a content calendar"), and the word "multiple" distinguishes it from the singular sibling delete_calendar_row and from delete_content_calendar. It stops short of naming those siblings explicitly, so an agent must infer the distinction from the name and pluralization.

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 call this rather than delete_calendar_row, delete_content_calendar, or unschedule_calendar_row. The parenthetical exclusion is a behavioral note, not usage guidance, so the agent is left to infer bulk-delete intent from the name alone.

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