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

No annotations are provided, so the description carries the full behavioral burden, yet it only discloses billing cost (1 credit per call). It says nothing about caching, auth requirements, or whether a missing/private video errors or returns null. The lone billing note is genuinely useful but far short of full disclosure for an unannotated tool.

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 and front-loaded, but the content is padded with metadata labels ('Group: Specific video Info', 'Billing per call') and the leading bold '**string**' is a stripped return-type token rather than a description. It is terse without being informative.

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 trivial one-parameter getter with no output schema, the description at least signals the return type (a localized string title) and the cost, which is the minimum an agent needs. However, it omits any statement of purpose beyond the field name, leaving overall completeness adequate but thin.

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?

With one parameter and 100% schema description coverage, the schema already documents the video ID format and its regex constraint. The description adds nothing about the id parameter, so the baseline 3 applies.

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 text '**string** The localized video title' largely restates the tool name (get_info_title) and reads as a return-type annotation rather than a statement of what the tool does. It does not specify a verb or scope, and gives no way to distinguish it from the eleven sibling get_info_* field getters beyond its 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 when-to-use guidance, no mention of alternatives such as get_info (which presumably returns the full info bundle), and no conditions under which this single-field getter is preferred. The only usage-adjacent content is the credit cost.

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