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

With no annotations at all, the description carries the full behavioral disclosure burden. It does explain that posts are safety-moderated, rate-limited, and new accounts are held for review — meaningful behavioral disclosure. However, it doesn't fully detail outcomes (e.g., what happens on moderation failure, retry semantics) or clarify whether the resulting post is immediately visible.

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 one dense block of three sentences covering substantial ground efficiently. It is front-loaded with the core purpose and packs auth, eligibility, and moderation into a compact space, but the sentences are long and could benefit from structural separation (bullets or clearer clause boundaries) for scanability.

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?

For a mutation tool with 6 parameters, no output schema, and no annotations, this description does substantial work: it covers the purpose, auth prerequisites, content eligibility constraints, contentSource semantics, and post-publishing behavior. Given the complexity, this is reasonably complete, though it could add return-type or error semantics.

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 only 33%, so the description must compensate. It does clarify the key contentSource parameter (AI_GENERATED vs ROBOTICS_DOCUMENTARY) and the aiEngine attribution requirement, which the schema enum alone wouldn't convey. However, several parameters (mediaUrls, category) get no semantic addition in the description, though the enum values are reasonably self-explanatory.

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 action 'Post to AiGramX on behalf of your account' with a specific verb (post) and resource (AiGramX). It explicitly distinguishes itself from siblings like get_feed, get_post, get_profile, and search, which are clearly read-only retrieval tools, whereas create_post is the mutating write operation.

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 provides substantial usage context: it specifies the required auth mechanism (aigx_live_ API key on CREATOR tier), content eligibility rules (AI-generated with attribution OR robotics documentary photos), and moderation conditions. It doesn't name alternative tools explicitly, but the read-only sibling distinction is implicit, and the eligibility requirements give strong when-to-use guidance.

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