create_media_post

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

With no annotations, the description must disclose behavior but only implies creation. It omits details on authentication, side effects, authorization needs, or what happens during the operation. The optional account/cookies parameters are not explained in terms of their behavioral impact.

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 a single short sentence, which is concise but at the expense of essential details. It front-loads the action but omits two parameters, making it incomplete.

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?

The tool has 5 parameters, no output schema, and no annotations. The description is too minimal to provide a complete understanding of usage, return values, error handling, or required context. Sibling tools further underscore the need for more context to distinguish this tool.

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 only 40% (account and cookies have descriptions). The description lists mediaType, prompt, mediaUrl but adds no semantics about their formats, constraints, or allowed values. It also omits the account and cookies parameters entirely, failing to compensate for the schema gaps.

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 it creates a 'Grok media post' from three components, which gives a basic idea but is vague about what 'Grok media post' entails. It does not differentiate well from sibling tools like 'create_project' or 'agent_send' that may also create posts.

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 is provided on when to use this tool versus siblings, nor on prerequisites or conditions. The description lacks any context for appropriate usage.

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