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

With no annotations supplied, the description carries the full burden and does add real behavioral context beyond the schema: it warns that creator metadata may contain HTML, that reuse terms must be verified on the file page, and that calls consume the caller's OpenAny gateway credentials with charges and authorization determined by the gateway. It stops short of stating read-only semantics or rate/limit specifics, but the caveats it does give are substantive.

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 payload-relevant content is front-loaded in the first sentence, and the HTML warning and attribution note are short and useful. The two trailing gateway sentences are boilerplate that would ideally be shared across all tools rather than repeated per definition, but they are compact and not disruptive.

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 usefully enumerates the returned fields, and it flags the HTML caveat and licensing caveat a consumer needs. For an eight-required-parameter read tool with all enums locked down, the remaining gap is minimal: mainly the absence of guidance on locating a valid file title.

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 100% and six of eight parameters are fixed enums, so the schema already does the heavy lifting. The description names the kinds of data the parameters retrieve but adds no syntax or format guidance (for example, the required 'File:' title prefix lives only in the schema), which is the expected baseline-3 outcome.

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 opens with a specific verb ('Get') and enumerates exactly what is returned (original/thumbnail URLs, dimensions, MIME type, creator and license metadata), which is well beyond restating the name. It distinguishes itself implicitly from the commons search sibling by returning per-file details, but it never names that sibling or states that a title is needed, so full sibling differentiation is missing.

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 context is only implied: the tool is for inspecting a single Commons file, and the caller is told to 'Check the file page for attribution and reuse terms' when reusing the asset. There is no explicit statement about when to use this versus wikimedia_get_commons_search to locate a file, and no prerequisite guidance such as where the required title comes from.

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