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

Annotations already declare the safety profile (`readOnlyHint`, `idempotentHint`, `destructiveHint=false`), and the description adds useful context about the return contents: each section includes `type`, `note`, and `example`. It does not cover permissions or error behavior, but for a read-only introspection tool this is solid.

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 [read] tag and resource scope are front-loaded, and the two sentences contain no filler. It efficiently covers both the return structure and the optional-key behavior.

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?

There is no output schema, so the description must explain return values, and it does by listing the returned sections and the `type`/`note`/`example` fields. It could be slightly more explicit about the exact response shape, but it is complete enough to select and invoke 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%, so the description must carry parameter meaning. It does: the optional `image_key` value selects one section, and omitting it returns all sections; the available sections are listed. The wording slightly conflates 'image key' with section key, but the intended usage is still clear.

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 resource and scope: an image's `image_project` document and `image_output` settings, and it enumerates the sections returned. This distinguishes it clearly from sibling variable-lookup tools such as `get_website_variables` or `get_template_variables`.

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 explains how to use the optional key: pass one section key to narrow results, or omit it to get all sections. However, it does not explicitly say when to choose this tool over alternatives or when it is not appropriate.

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