google_ads_upload_store_sales

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

No annotations are provided, so the description must disclose behavioral traits. It notes using the same upload mechanism as offline conversions and gives a detailed example, but lacks specifics on authentication, success/error handling, or rate limits. The returns field is minimal ('Upload success message'), adding limited behavioral insight.

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 concise with clear sections: purpose, args, returns, example, note. Every sentence adds value with no redundancy. It is well-structured and easily readable.

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?

The description covers purpose, parameters, and an example, but lacks details on error handling, validation rules, or prerequisites. Given the complexity of store sales uploads, more completeness (e.g., requirements for gclid format or timestamp format) would improve usability. Output schema is not provided but returns description is minimal.

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?

Input schema has 0% coverage with no descriptions. The description compensates with an Args section explaining each parameter: customer_id format, conversion_action_id type, and store_sales as a list with keys. The example further clarifies the structure. This adds substantial meaning beyond the schema.

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 states 'Upload store sales data (in-store purchases from online clicks)' and 'specialized form of offline conversion upload for retail businesses tracking in-store purchases that originated from online ads', providing a specific verb and resource that distinguishes it from other upload tools like google_ads_upload_offline_conversions.

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 implies the tool is for store sales conversions but does not explicitly state when to use it versus alternatives like google_ads_upload_offline_conversions. The sibling list includes multiple upload tools, so clearer guidance would help. However, the specialized labeling provides enough context for informed selection.

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