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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered without the description. The description adds no further behavior beyond that — nothing about resolution failures, what an invalid media_ref yields, or how connection_context scopes the read. Given the annotation coverage this is acceptable but thin.

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?

A single clause plus a semicolon-delimited routing note. Zero filler, and the core action is front-loaded before the alternative is mentioned.

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?

An output schema exists, so return values need not be described, and annotations cover the safety profile. What remains missing is parameter meaning, particularly the opaque connection_context token and the provenance of media_ref, which an agent would need to call this 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% for both parameters, so the description carries the burden and does not meet it. It never explains the media_ref format (the schema's own pattern hints at a 'media_e1.' prefix but no rationale) or what connection_context is used for. The generic phrase 'account media reference' is the only semantic hint provided.

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 names a specific verb and resource ('Read one account media reference'), and the word 'one' cleanly separates it from the batch sibling. It does not explicitly distinguish itself from account_media_list, but the singular/plural framing makes the distinction inferable.

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 gives an explicit routing rule: 'prefer account_media_get_batch for multiple selections'. That is a real when/when-not statement tied to the count of selections. It stops short of mentioning account_media_list or any prerequisite about the media_ref origin.

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