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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does not state whether this is a read-only operation, what the return format is, any side effects, or authentication requirements. The description only hints at the data content, not the tool's behavior.

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 description is a single short sentence with no fluff. It is concise to the point of being terse, but it does not waste words. However, the brevity comes at the cost of necessary information, so the structure is acceptable but not exemplary.

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?

Even though the tool is simple (one parameter, no output schema), the description is far from complete. It does not explain what 'data' refers to, what a 'media source' is, what the query does, or how the response is structured. With multiple siblings covering related media concepts, the lack of differentiation and usage context makes the description inadequate for any real agent.

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?

The schema has one optional 'query' string parameter with 0% coverage in the description. The description does not explain the purpose or format of the query parameter, nor how it filters the results. For an agent to use it correctly, the description must compensate for the schema's lack of description, and it fails completely.

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 the domain (media sources) and the kind of information (licence, redistribution), but lacks an explicit verb like 'list' or 'retrieve'. It is distinguishable from siblings by name but not through any active phrasing. It gives a vague purpose that an agent could infer but not rely on.

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?

No guidance is provided on when to use this tool versus siblings like media_outlets or media_verify. There is no mention of prerequisites, context, or exclusions. An agent must guess the scope from the name alone.

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