get_image

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

With no annotations, the description carries the full burden. It states the tool returns state, implying read-only behavior, but does not disclose prerequisites (e.g., image existence), side effects, or other constraints. It provides minimal behavioral context.

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 a single concise sentence listing return fields, front-loaded with the main purpose. It could be improved by structuring parameters separately, but it is short and to the point.

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?

The description covers only return values. Without output schema, annotations, or parameter explanation, it is incomplete for a simple getter tool. It lacks critical information about inputs and usage 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 description does not mention the required parameters 'name' and 'path'. Given 0% schema description coverage, the description must compensate, but it only describes return fields, leaving parameter meaning entirely undocumented.

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 'Return effective state of a named Image' with a specific verb and resource, and lists the fields returned (position, size, Source, etc.), distinguishing it from sibling getters like get_chart or get_dataset.

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?

The description implies usage for retrieving image state, but does not provide explicit guidance on when to use this tool versus siblings like get_embedded_image_data or set_image_* tools. No when-not or alternative guidance is given.

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