microcms_update_content_reservation

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

With no annotations, the description discloses key behavioral traits: setting both times, clearing all when both omitted. It implies that providing only one time sets that one, but does not explicitly state that the other remains unchanged. This is a minor gap but overall transparent.

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 concise sentences. The first states the purpose, the second gives usage instructions. No redundant information, front-loaded with key details.

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?

The description covers the essential behaviors (setting and clearing) and the parameters involved. It does not describe return values, but the tool has no output schema. Overall, it is sufficient for an agent to correctly invoke the tool.

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 100%, so baseline is 3. The description adds value by explaining the clearing behavior when neither time is provided, which is not in the schema. Examples of ISO 8601 formats are also given, reinforcing the schema descriptions.

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 clearly states the verb 'Set or clear' and the resource 'content publish/stop reservation schedules' in the microCMS Management API. It distinguishes this tool from siblings by focusing specifically on reservation management, which is unique among the listed siblings.

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?

The description provides explicit guidance on how to use the tool: provide publishTime and/or stopTime, and if neither is provided, existing reservations are cleared. It does not explicitly state when to use this tool over alternatives, but the context of reservation scheduling is clear and distinct from other update tools.

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