get_content_calendar

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

No annotations are provided, so the description fully covers behavioral aspects: it returns entries with native-language Reels hook and hashtag set, uses verified lunar/astronomical dates, and lists available markets. It doesn't mention rate limits or authentication, but as a read operation, this is acceptable.

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 description is two sentences, front-loading the main purpose and filters. The list of markets is detailed but necessary for usability. Every sentence adds value, though it could be slightly more concise by grouping markets differently.

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?

Given the tool has 5 parameters, no output schema, and no annotations, the description covers the essential functionality: return entries with filters. It explains the niche filter and market list. A minor gap is the lack of explicit return format, but it mentions the entry contents sufficiently.

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 baseline is 3. The description adds value by explaining that entries carry a Reels hook and hashtag set, and that dates use verified anchors. It also clarifies the 'niche' parameter matches the calendar entry's niches array, going beyond 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 tool returns Instagram content calendar entries for a market, with optional filters. It uses a specific verb 'Return' and resource 'content calendar entries', and distinguishes from sibling tools that focus on hashtags or downloads.

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 explicitly states when to use the tool (to get calendar entries for a market) and provides guidance on using 'GLOBAL' for cross-market dates. It doesn't explicitly state when not to use it or list alternatives, but the sibling tool names imply different use cases.

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