ga4_create_skadnetwork_conversion_value_schema

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

No annotations provided, so description carries full burden. Only states it is a write operation via '[GA4 WRITE]' and the need for confirm. Does not discuss reversibility, authorization requirements, rate limits, or consequences of creation.

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 sentences, no wasted words. First sentence front-loads purpose and action. Second sentence covers input and requirements efficiently.

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 no output schema and 4 parameters, the description explains the tool's purpose, key requirements, and how to provide settings via body. Could mention response details but not necessary. Adequate for a create tool with good schema coverage.

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 baseline is 3. Description adds meaning by stating that 'body' is used for 'postbackWindow settings', which helps an agent understand how to use the body parameter beyond its generic schema description.

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?

Starts with '[GA4 WRITE] Create' clearly stating action and resource. 'SKAdNetwork conversion value schema on an iOS data stream' identifies the specific object. Distinguishes from sibling tools like ga4_update_skadnetwork_conversion_value_schema and ga4_delete_skadnetwork_conversion_value_schema by using 'Create'.

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?

Specifies input via 'body' and prerequisites: 'Requires GA4_MCP_ENABLE_WRITES=true and confirm=true'. Provides clear context for use, though does not explicitly exclude scenarios or name alternatives.

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