ghl_social_start_edit_session

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

The description adds value beyond annotations by explaining that changes are staged until saved or discarded, and it specifies the endpoint and OAuth scopes. This provides behavioral context that complements the annotations, though it doesn't mention potential side effects like locking.

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, front-loading the main purpose, and includes additional context like endpoint and scopes without unnecessary fluff.

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 complexity (nested parameters, no output schema), the description could be more complete by explaining the body structure and what the session enables. It adequately covers the basic flow but lacks detail on return values or post-session steps.

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?

The description does not explain the parameters (queueId, body) beyond the schema. With 50% schema coverage, the description should clarify the parameter meanings, but it adds no semantic value.

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's purpose: starting or resuming an edit session for queue items, with a draft copy created. This distinguishes it from sibling tools like ghl_social_discard_edit_session and ghl_social_save_edit_session.

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 mentions 'Start or resume an edit session' but does not explicitly provide guidance on when to use it versus alternatives, such as prerequisites or when not to use it. The OAuth scopes are listed but no usage context beyond that.

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