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

Annotations already declare readOnlyHint=true, so safety is covered by structured data. The description adds value by naming the fields returned, but says nothing about behavior on a missing asset, permission requirements per domain, or whether metadata is cached/stale.

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 front-loaded sentence with no filler, and the resource plus return fields come first. It is efficient but lacks any structural cues (e.g., a note on the required identifiers) that would make it more than lean.

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 a two-parameter read call with no output schema and only a readOnlyHint, the description covers purpose and return fields. However, it leaves the 'domain' parameter entirely unexplained and gives no failure or scoping behavior, which an agent needs 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%, so both required parameters (id, domain) are undocumented in structured fields. The description only weakly implies that 'id' identifies the asset; 'domain' is never explained — no format, no accepted values, no indication of what domain scopes the lookup.

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 gives a specific verb ('Get') and resource ('details for a single media asset') and enumerates the fields returned (URL, dimensions, format, metadata), which implicitly separates it from siblings like upload_media and get_media_upload_url. It stops short of explicitly naming those siblings, so differentiation is inferred rather than stated.

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 only implied: 'single' hints that this is the per-asset lookup rather than a listing or upload operation. There is no explicit when-to-use, no mention of prerequisites, and no pointer to related tools such as get_media_upload_url or fetch for other asset types.

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