ghl_social_fetch_edit_session_calendar

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

The description uses 'Fetch' and 'Retrieves' suggesting a read-only operation, but annotations set readOnlyHint to false, indicating potential side effects. The description does not disclose side effects, rate limits, or authorization details beyond the OAuth scopes listed. This contradicts the annotation.

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 two sentences plus endpoint/scopes. It is front-loaded with the title-like first sentence. Every sentence adds value, though it could be more structured (e.g., bullet points for parameters).

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 no output schema, the description does not explain the return format or error handling. It explains the purpose (preview of unsaved changes) but omits details like pagination or filtering behavior. The endpoint and scopes are provided, but completeness is moderate for a tool with nested body parameters.

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 50% with queueId lacking a description and body having a generic one. The description adds minimal parameter meaning, only hinting at 'draft items within an edit session' which implies sessionId usage. Nested properties are described in schema but queueId's purpose remains unclear.

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 'Fetch[es] calendar view for an edit session' and explains it retrieves a calendar preview of scheduled posts based on draft items in an edit session. This distinguishes it from siblings like ghl_social_fetch_calendar_list (which fetches actual calendar) and ghl_social_save_edit_session (which commits changes).

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 context ('shows how posts would be scheduled if changes were saved') but does not explicitly state when to use this over alternatives, such as comparing to ghl_social_fetch_calendar_list or ghl_social_start_edit_session. No when-not-to-use guidance is provided.

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