postmediabyfilename

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

The description discloses only the body format (raw binary). No annotations exist. There is no mention of required permissions, error conditions, size limits, or what happens after upload. The agent is left blind to critical behavioral traits.

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?

While the description is short, it is under-specified rather than concise. It front-loads the body format but omits purpose and usage context. The sentence does not earn its place because it lacks substance to guide tool selection.

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 absence of annotations and output schema, and the complexity of 8 parameters with 2 required, the description is critically incomplete. It fails to explain what the tool does, when to use it, or how parameters interact, making it nearly useless for an AI agent.

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 schema covers 75% of parameters with descriptions, so the bar is higher. The description adds zero parameter information; it does not clarify how parameters like group_id or file_name relate to the raw binary body. This provides no value beyond the schema.

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 'POST body should contain raw binary media file' does not state the tool's purpose. It only specifies the request body format, leaving the reader to infer from the name that it posts a media file. This is insufficient for distinguishing from siblings like postmedia or postmediamultipart.

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 alternatives. With many sibling media tools, the agent has no basis to select this one over postmedia (likely JSON) or postmediamultipart (multipart upload).

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