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

With no annotations, the description must carry the full behavioral load. It does disclose the output shape (format_version 1, rows, default_targets, calendar_bundle), which is real added value, but it omits whether the call is read-only, any size limits or pagination on large calendars, and whether default_targets are resolved or raw.

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?

Two short sentences with the output format and the payload keys front-loaded, followed by the practical purpose. Zero filler and no repetition of the tool name.

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, so the description must cover return values — it does so at a useful level (format_version, rows, default_targets, calendar_bundle). Missing only safety/read-only disclosure and large-export behavior, which are modest gaps for an export utility.

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 100%, so calendar_id and publisher_pid are already documented. The description adds nothing on parameters beyond naming payload fields, and the third parameter (notification_message) is not addressed at all in the description, so the baseline 3 holds.

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 ('Pull a content calendar as portable JSON') plus the payload contents (rows, default_targets), which distinguishes it from the read-only get_content_calendar. It never names the obvious counterpart import_content_calendar_json, so sibling differentiation is only implied.

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?

'Save calendar_bundle for git or edit offline' implies the use case (backup/versioning/offline editing), but there is no explicit when-not or direction to the import counterpart for round-tripping. An agent must infer that export pairs with import rather than being told.

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