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

The readOnlyHint annotation already communicates that this operation is safe and non-destructive. The description reinforces this by describing a listing operation and ties it to a pre-deletion workflow, giving useful context without contradicting the annotation.

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 compact and information-dense, covering purpose, output fields, usage context, and prerequisite in one sentence. It has no filler or redundant wording.

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 simple list-by-ID tool, the description is complete: it states what is returned, why you would use it, and the required setup step. The reference to delete_doc_image also gives necessary surrounding workflow context.

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 fully documents the single documentationId parameter as a public Guid. The description adds the clarifying context that this ID refers to the documentation whose inline images are listed, which is helpful but not a major extension 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 clearly states the tool lists inline images of a documentation and specifies the exact returned attributes (file name, URL, size, dimensions, reference status). It also distinguishes its purpose as finding orphaned uploads before deletion, setting it apart from related doc tools.

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?

It explicitly says this is how you find orphaned uploads before calling delete_doc_image, giving a clear when-to-use context. It also states the prerequisite of project context and instructs to call set_context first, leaving no ambiguity about setup.

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