getMultiImagePostPhoto

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint, and openWorldHint. The description adds value by explicitly stating 'Read-only' and detailing the return format including the structure of the response for found and not found cases, which goes beyond annotation hints.

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 concise and well-structured with clear sections: a one-line summary, a lean-by-default keep-list, usage guidelines, required parameter, see also, and return format. Every sentence is purposeful and front-loaded.

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 the tool's simplicity (single record fetch by ID), the description fully covers purpose, parameters, return format, error behavior, and relationship to sibling tools. Annotations cover safety, and output schema is not needed due to explicit return format description.

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 adds meaning beyond the schema by explaining the default keep-list fields and the purpose of 'include_marketplace' parameter. For 'photo_id', it emphasizes it is required and how to obtain it. The schema provides some description for 'include_marketplace', but the description adds contextual usage guidance.

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 'Get a single album photo - Fetch a single portfoliophoto record.' It distinguishes the tool from the sibling 'listMultiImagePostPhotos' by explicitly mentioning 'single' and comparing to the list counterpart.

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 provides explicit usage context: 'Use when: editing or removing one specific photo within an album.' It also mentions the required prerequisite 'photo_id (from listMultiImagePostPhotos)' and references the sibling tool 'listMultiImagePostPhotos' for enumeration.

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