get_creator_posts

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds valuable behavioral context: platform-specific page limits (Instagram 12/page, TikTok max 35, YouTube max 50), cursor-based pagination, and cost per request. No contradiction with annotations, and it provides useful operational details beyond the schema.

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 three concise sentences, front-loaded with the primary action. Every sentence adds meaningful information without filler, making it efficient and easy to parse.

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?

With an output schema present, annotations, and 100% schema coverage, the description sufficiently covers the remaining contextual aspects: platform variance, pagination behavior, and cost. It is complete for an agent to select and invoke the tool correctly.

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?

Since schema coverage is 100%, the baseline is 3. The description adds meaning by specifying exact platform limits (which the schema only vaguely references as 'platform limits apply') and explicitly mentioning cursor-based pagination, enriching the semantics of count and pagination_token.

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 retrieves recent posts/content from a creator, with a specific verb and resource. It further distinguishes itself by mentioning per-platform limits, which separates it from sibling tools like get_post_details and discovery tools.

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 when a creator's recent posts are needed, but it does not explicitly name alternatives or when-not-to-use scenarios. Sibling tool names suggest alternatives, but the description doesn't reference them, leaving usage guidance implicit rather than explicit.

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