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

The read-only, idempotent, non-destructive, and closed-world annotations already cover the safety profile. The description adds that the resource is private and that supported formats are PNG, JPEG, and WebP, but it does not disclose the return shape (binary data vs. URL), access requirements, or failure behavior for invalid or unauthorized resource IDs.

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 a single front-loaded sentence with no filler. It is appropriately concise, though it may be too terse for the amount of missing context.

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 an image retrieval tool with no output schema, the description should clarify whether the return value is binary image data, a URL, or another structure, and how to source the required resourceId. It covers only the basic action and allowed formats, leaving important invocation and return-value context 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 one required parameter, resourceId, with 0% schema description coverage. The description implies it identifies the resource but adds no meaning about its format, where to find it, or its relationship to list/search results, so it does not compensate for the schema gap.

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 action ('Returns') and resource type ('PNG, JPEG, or WebP context resource'), which makes the basic purpose clear. However, 'context resource' is vague compared to the title's 'project context image,' and the description does not differentiate this from sibling retrieval tools such as websiteKnowledge_read or webResearch_viewImage.

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 gives no guidance on when to use this tool versus websiteKnowledge_read, websiteKnowledge_list, websiteKnowledge_search, or webResearch_viewImage. It also does not explain how to obtain a valid resourceId, which is required to invoke the tool.

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