video_query

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds a genuine behavioral constraint (paging params are required) and the shape of each returned item (has a `video_id`), but says nothing about rate limits, filtering scope, or whether results are exhaustive.

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?

Three short sentences, no filler, with the core purpose front-loaded before the paging detail. The example is compact and directly actionable.

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 re-explained, and the tool is simple (2 params, no required fields). However, the description leaves open what 'query' actually filters on and never accounts for `account_key`, so it is only minimally sufficient for correct invocation.

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 coverage is 0% and the schema only shows `params` as an opaque anyOf object, so the description carries the load: it names the concrete keys (current_page, page_size) and their example values, which is meaningfully more than the schema. The `account_key` parameter remains unexplained, keeping this short of a 5.

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?

States a specific verb+resource ('Query the seller's videos') and adds the intent ('to find video ids'), which is more than a restatement of the name. It does not explicitly contrast with siblings like video_list_related or video_relate_product, so the differentiation is left implicit.

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?

The description gives a concrete calling pattern ('Requires paging params, e.g. params={"current_page": "1", "page_size": "20"}'), which implies how to invoke it. It never states when this tool should be chosen over video_list_related or video_relate_product, so there is no real alternative-selection guidance.

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