ghl_social_get_posts

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

The description implies a read operation ('Get posts') and includes a read-only OAuth scope, but annotations set readOnlyHint=false. This contradiction is not resolved. No additional behavioral context (e.g., side effects, pagination behavior) is provided beyond annotations.

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 short but contains redundancy ('Get posts' repeated). It front-loads the purpose and adds endpoint details, but could be more concise.

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?

No output schema is provided, yet the description does not describe the response format (e.g., list of post objects). The use of POST method for retrieval is not explained, leaving the agent without full context.

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 the schema already documents all parameters. The description adds no parameter-level information beyond the schema, hitting the baseline.

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 states 'Get posts' clearly, but it is repetitive and does not explicitly distinguish from the sibling tool 'ghl_social_get_post' which likely retrieves a single post. The endpoint indicates a list operation, but this is not highlighted.

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?

No guidance on when to use this tool versus alternatives like ghl_social_get_post or ghl_social_get_statistics. The description provides no context about appropriate scenarios or exclusions.

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