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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral context beyond the annotations: pictures are returned as images and folders return a file listing, which tells the agent what shape of result to expect.

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?

One front-loaded sentence beginning with the verb and resource, with no filler. It is somewhat dense and runs long due to the enumeration, but every clause carries 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?

No output schema exists, so the description must signal return shapes, and it does (image for pictures, listing for folders, file contents otherwise). With only two fully-described parameters, this covers what an agent needs to call it 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 coverage is 100%, so the baseline is 3. The description goes beyond the schema's single example (recipe/RECIPE.md) by naming other valid paths and explaining that inputs.json's media field references the user's own uploaded files, which helps the agent construct paths.

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?

States a specific verb (read) and resource (files of the recipe a project was started from), and enumerates the concrete contents (brief, structure.json, inputs.json, user-written files, pictures). It is clear what the tool does, though it never names siblings like show_recipes or start_recipe to sharpen the boundary.

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?

Usage is implied by the enumeration of readable artifacts rather than stated: the reader infers 'call this to inspect recipe contents' and that a folder path yields a listing. There is no explicit when-not or pointer to show_recipes/start_recipe for the alternatives.

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