tools_remotion_src_onboarding_videos_google_ads

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

The description provides no behavioral information beyond the stated action. Annotations are absent, and the description does not disclose side effects, required permissions, or what happens when the tool is invoked.

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 very concise, using a single line to convey the tool's purpose. It is front-loaded with the key information, but it could benefit from slightly more structure.

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?

Given the tool's potential complexity (video generation with arguments), the description is too minimal. It does not explain how to use the tool effectively, what the video will contain, or any details about the expected arguments.

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 input schema has 100% coverage for its single parameter ('args') with a description of 'Key-value arguments passed to the script via stdin'. The tool description adds no additional meaning beyond the schema, which is adequate for a generic parameter.

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 clearly identifies the tool as focusing on Google Ads manager (MCC) link and GA4 Editor for conversion import. It distinguishes from sibling tools (e.g., meta_ads, tiktok_ads) by specifying the platform. However, it lacks an explicit verb (e.g., 'creates', 'generates') and uses acronyms (MCC, GA4) that may be unclear.

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 alternatives. There is no mention of prerequisites, constraints, or scenarios where this tool is appropriate or not.

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