public_get_media_info

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered externally. The description adds nothing beyond that — no note on auth requirements, whether the caller must own the order, or what happens for missing media.

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?

It is short, but that shortness is under-specification rather than economy — a three-word fragment with no verb object detail or scoping. Nothing is front-loaded because there is nothing to load.

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 tool requiring two IDs and returning unspecified output with no output schema, the description should at least indicate what media info is returned and how it ties to the order. The public_* sibling family implies an order-scoped lookup, but the description never states or confirms this.

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%, with both media_id and order_id documented inline, so the baseline of 3 applies. The description contributes no additional meaning about the two required IDs or their relationship.

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?

"Get Media Info" essentially restates the tool name with no added specificity — it does not say which media, in what context, or how it differs from siblings such as get_resource_metadata or public_get_order_deliverables. A reader learns nothing beyond the name.

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?

There is no guidance on when to call this tool, when not to, or what alternatives exist (e.g., other public_get_* order endpoints). The description provides zero routing information for an agent choosing among hundreds of siblings.

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