ghl_social_fetch_calendar_list

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

Annotations exist but don't fully clarify read-only behavior (readOnlyHint=false though it's a read operation). The description adds endpoint and OAuth scopes but doesn't disclose potential side effects or behaviors beyond the obvious fetch operation.

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 concise with three sentences covering purpose, return, filtering, endpoint, and scopes. It is front-loaded but could be slightly more compact.

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 explains what is returned (scheduled posts) and filtering options, but lacks details on pagination, response format, or how calendar view is structured. Given no output schema, more context would be helpful.

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 the schema already documents parameters well. The description adds minimal extra meaning beyond restating 'date range' and 'filtering by categories and accounts'. Baseline 3 is appropriate.

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 it 'Get scheduled posts calendar view' and explains it returns scheduled posts from active queues within a date range, with filtering by categories and accounts. This is specific and distinguishes from sibling tools like ghl_social_get_posts or ghl_social_fetch_queues.

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 implies usage for a calendar view of scheduled posts but provides no explicit guidance on when to use this tool over alternatives. No when-not-to-use or sibling comparisons are mentioned.

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