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

Annotations carry only a title, so the description bears the full behavioral burden. It implies a mutation ('Edit') and an ownership requirement, but says nothing about which fields are mutable, whether edits are reversible, or what auth/permission level is needed.

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?

A single short sentence with a clear verb-first structure and no filler. It is efficient, though its brevity borders on under-specification rather than true conciseness.

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 no annotation hints, no output schema, and zero parameter documentation, the description leaves the agent guessing about editable fields, preconditions, and results. The ownership clause is the only genuine addition.

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 0% across all four parameters, so the description must compensate and largely fails. The word 'metadata' loosely gestures at title/description/tags, but the required 'id' selector and the accepted format for tags (array of what?) remain unexplained in both the schema and the description.

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?

Names a specific verb ('Edit'), resource ('metadata on an image'), and a scope constraint ('an image you own'), which separates it from siblings like images_delete, images_generate, and images_upload. It stops short of naming any sibling explicitly, so differentiation is by inference rather than statement.

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?

There is no guidance on when to prefer this over images_upload, images_share, or images_delete, and no exclusions are given. The only usable signal is the ownership phrase, which hints at a precondition but never states it as a rule.

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