Validate bulk-change CSV

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, and the description reinforces this by saying it won't upload or change the platform. It adds useful detail about what exactly gets validated (columns, required values, allowed values, row limits), which is beyond the annotations.

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, tightly written sentence with no filler. Key behavioral constraints are front-loaded, and every phrase adds information.

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?

With no output schema and no parameter descriptions, the description should explain what templateKey refers to, what the CSV must look like, and what the tool returns (e.g., validation report vs. throwing errors). It is missing all of that, so an agent would struggle to invoke it correctly despite the clear high-level purpose.

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 description coverage is 0%, so the description must explain what 'templateKey' and 'csv' mean and how they should be supplied. It does neither; it only describes the validation behavior generically, leaving the agent to guess the role of templateKey and the expected CSV format.

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 names a specific action ('Validate') and resource ('bulk-change CSV'), and lists the validation dimensions: columns, required values, allowed values, and row limits. It is clear enough to separate this from sibling tools like gtm_generate_bulk_template, though it does not explicitly name an alternative.

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 phrase 'without uploading or changing a platform' implies this is a pre-flight check before an actual change, giving some context. However, it does not explicitly state when to use this tool versus siblings or when not to use it.

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