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

Annotations already declare this as a read-only, idempotent, closed-world, non-destructive operation. The description adds useful context by saying results are real photos from the user's own library, ranked by fit to the post topic, and that setting an image is handled separately by change_image. It does not mention auth needs or limits, but the annotations already cover safety behavior.

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 compact sentences with no wasted clauses. The core behavior is front-loaded, followed immediately by the practical handoff to change_image.

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 single-parameter read-only recommendation tool with rich annotations and no output schema, the description covers what is returned, where the photos come from, ranking, and how to use the result. Nothing an agent needs in order to call it correctly appears to be missing.

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?

There is only one parameter, postId, and schema description coverage is 100%, so the schema already explains it. The description reinforces that a post ID is required but does not add syntax or format details 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 states a specific verb and resource: return ranked, best-matching real photos from the user's own library for a given post's topic. It clearly scopes the tool to post-specific recommendations, though it does not explicitly contrast itself with siblings like search_my_images.

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 says the tool is ideal for AI-OFF customers and tells the caller to pass a chosen URL to change_image to actually set the image. That gives clear usage context and a downstream action, but it does not state when not to use this tool or name alternative recommendation tools.

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