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

Annotations already declare readOnlyHint/idempotent/openWorld=false, so safety is covered; the description adds genuinely new behavioral meaning by defining the four advice categories and what each implies for posting (no promotional posts, respectful only, greeting allowed). It does not mention the 60-day default window, the 400-day cap, or that omitting traditions returns all of them, leaving some behavioral gaps.

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 resource scope is front-loaded in the first clause, followed by the advice taxonomy and then the actionable directive. The long parenthetical tradition list is bulky but earns its place by scoping the tool; a single wasted clause would be easy to find, but overall it is tight.

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?

With zero required params, no output schema, and mid-level schema coverage, the description carries the burden of explaining what comes back — and it does, via the per-day advice categories. It omits the default range (today to +60 days) and language behavior, but the schema covers those, so nothing critical for correct invocation is missing.

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 75% and the schema already documents from, to, and traditions (including the enum list). The description's tradition enumeration largely restates the schema, and it adds nothing about the `language` parameter or the default date window, so it is at the baseline for a well-covered schema.

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 resource (holidays across enumerated traditions) plus a distinctive value-add: per-day posting advice classified as avoid/sensitive/opportunity/normal. An agent immediately knows what comes back and that it is not a generic calendar lookup; no sibling tool covers this territory.

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?

"Check this before scheduling" gives an explicit workflow trigger that ties this tool to schedule_post/create_post, and "match the traditions to the audience of each account" tells the agent how to parameterize by audience. It stops short of naming the specific sibling tools or stating when not to call it, so it is clear context rather than full when/when-not guidance.

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