set_image_source

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

Discloses behavioral traits: refusal on dangling reference, idempotency, side effects (sets Source=Embedded, rewrites Value). No annotations provided, so description fully covers transparency.

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?

Well-structured and concise: purpose, behavior, error, prerequisite, idempotency, return format. Each sentence adds value.

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?

Covers return format, error cases, prerequisites, and idempotency. No output schema, but description adequately explains results.

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?

Adds meaning beyond schema: explains embedded_name must exist in EmbeddedImages. Schema coverage is 0%, but description does not elaborate on path or image_name beyond names, which are somewhat 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?

Clearly states purpose: repoint an existing Image to a different embedded image entry. Uses specific verbs (repoint, sets, rewrites) and distinguishes from delete-and-readd.

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?

Provides explicit when-to-use, prerequisite (add_embedded_image), error behavior for dangling references, and idempotency. Contrasts with alternative approach.

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