load_image

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

Annotations already indicate readOnlyHint=false and destructiveHint=false. The description adds that the tool loads an image from a tarball and that the data is base64-encoded bytes. It does not mention potential overwriting of existing images, but given annotations and context, the behavior is adequately transparent.

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 two sentences plus a brief args/returns section. It is front-loaded with the core purpose, followed by usage guidance. Every sentence adds value without redundancy.

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?

Given one parameter and no output schema, the description covers the tool's purpose, input, and return value ('list of loaded image attrs dicts'). It also addresses when to use an alternative. The description is sufficient for an agent to select and invoke the tool correctly.

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 has one parameter 'data' with format binary but no description. The description adds 'data - Tarball contents', clarifying the parameter's purpose. While it doesn't explicitly state 'base64-encoded' in the param section, the overall context makes it clear. For a schema with 0% description coverage, this is helpful.

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 'Load an image from a tarball produced by save_image', which provides a specific verb ('Load') and resource ('image') along with the origin ('tarball'). It distinguishes itself from the sibling 'load_image_from_file' by highlighting the difference in data transfer method (base64-encoded bytes vs streaming from disk).

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 explicitly tells when to use this tool vs the alternative: 'For a tarball already on the host running this server, prefer `load_image_from_file` — it streams from disk instead of carrying the (base64-encoded) bytes through the MCP protocol.' This provides a clear decision rule and context for tool selection.

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