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

The description adds nothing about side effects, permissions, or what happens to existing media. Annotations indicate destructiveHint=true and idempotentHint=true, but the description doesn't disclose any behavioral nuances beyond the raw endpoint. It is silent on what gets changed or replaced.

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 extremely terse (a single line), but it's under-specification rather than effective conciseness. It lacks any explanatory content, so it doesn't earn its place; it's just a stub.

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 tool with nested objects, an output schema, and a destructive hint, the description is grossly inadequate. An agent cannot determine what the operation does, what the parameters mean, or what the response looks like. It is essentially non-existent.

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 33%, and the description provides no parameter explanations. Only workspaceId has a description in the schema; body.mediaIds and path.id/channelId are undocumented. The description does not compensate for this gap at all.

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 is just the HTTP method and endpoint path (PUT /v1/posts/{id}/content/{channelId}/media). It identifies the verb and resource but does not explain what the operation does (e.g., attach media to a post's content). It's essentially a restatement of the tool name, which already contains 'put_posts_id_content_channelId_media'. There is no behavioral description.

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 siblings like post_media, delete_media_id, or patch_posts_id_content_channelId. The description provides no context about selection criteria, prerequisites, or alternatives.

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