create_conversion

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

DestructiveHint annotation already signals mutability. Description adds return value info but doesn't mention side effects like cost implications or that it creates a new resource. Moderate addition beyond annotation.

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?

Two very concise sentences with no wasted words. Purpose and return value front-loaded.

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 tool with 3 params, no output schema, and destructive annotation, description covers creation and return value but omits examples or guidance on parameter usage (e.g., value format, category examples). Adequate but not comprehensive.

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 100%, so description adds no extra parameter meaning beyond the schema. 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?

Clearly states verb 'Create a conversion action' and resource 'Google Ads'. Mentions return values (conversion ID and label for GTM setup), distinguishing it from retrieval tools like list_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?

No explicit guidance on when to use this tool vs alternatives like list_conversions or other creation tools. Lacks context about prerequisites or integration with GTM.

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