get_user_image

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose one non-obvious trait (the route is proxied in the docker image and bypasses the API in production), but omits authentication requirements, return content (image bytes vs URL), and error behavior for a 2-required-param endpoint.

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 definition is padded with an endpoint line, an irrelevant recipe-slug sentence, and a long comma-separated keyword tail (get, fetch, read, retrieve, view, show, read-only, mealie) that adds no decision-relevant information.

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 tool with no annotations, no output schema, and two undocumented required parameters, the description should carry the load; instead it spends most of its length on keywords and contains a contradictory slug statement, leaving the agent without what it needs to call 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?

Schema description coverage is 0% and neither user_id nor file_name is explained in the description. Worse, the description references a 'recipe slug' rather than the user_id/file_name pair, so what little it says about inputs is actively misleading.

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?

It does name the resource (user image) and gives the exact route GET /api/media/users/{user_id}/{file_name}, which is specific. But the sentence 'Takes in a recipe slug, returns the static image' directly conflicts with the actual parameters and muddies what the tool is for, leaving the agent less certain than a clean statement would.

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?

There is no guidance on when to choose this over siblings like get_logged_in_user, update_user_image, or get_recipe_img. The only usage-adjacent note ('should not hit the API in production') is a deployment caveat rather than a selection rule.

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