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

Annotations already cover the safety profile (readOnly, non-destructive, not open world). The description adds real behavioral context beyond them: the 60-day horizon, the warm-up gating rule, the notice-days requirement, and that the call is free. It stops short of pagination/error behavior, but for a read-only helper this is strong.

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?

Front-loads the core question, then packs constraints, return fields, usage guidance, and cost into a tight block. The mid-sentence enumeration of return fields is dense but every clause carries information; nothing is redundant with the schema.

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 enumerating earliestQueueDate, firstOpenDay, dailyCap, creditsPerPost, countsByDay/fullDays and warm-up progress is necessary and done well. Combined with the when-to-call guidance, an agent has everything needed to invoke and interpret the result.

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% for the single accountId parameter (UUID), so the schema already carries the semantics. The description adds no further syntax or format detail for the parameter, so the baseline 3 applies.

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 opening sentence gives a specific verb+resource — determining which days a managed account can accept posts — and immediately distinguishes it from the sibling list/publish tools. An agent can tell it answers a capacity/eligibility question, not a generic account lookup.

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?

Explicitly states the trigger condition and the alternative: 'Call this before publish_to_managed_account to pick a legal queueFor day.' It names the consuming tool and the downstream decision, which is exactly the routing guidance an agent needs.

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