ga_send_signup

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

Annotations already declare readOnlyHint=false, indicating a write operation. The description adds no further behavioral context such as authentication needs, rate limits, or side effects. It does not contradict annotations, but it also does not go beyond them.

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 short sentences, front-loaded with the primary action. Every word contributes to clarifying the tool's purpose and usage. No redundant or extraneous content.

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 simple tracking event, the description is adequate, but it omits details like whether user_id is required (it is not, but this is not clarified) and gives no explanation of client_id. There is no output schema, so return value is unmentioned. The minimalism is acceptable but leaves some gaps.

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 75%, with method, user_id, and user_properties described. The description itself does not explain any parameters. The missing client_id description remains unaddressed, but the schema provides enough for most parameters. Baseline 3 is appropriate given partial schema coverage.

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 uses a specific verb ('Send') and resource ('a sign-up event to Google Analytics'), clearly distinguishing it from siblings like ga_send_login and ga_send_purchase. It states exactly what the tool does without ambiguity.

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 states that this is the 'Standard event for tracking new user registrations,' which clearly implies when to use it. While it does not explicitly name alternatives or exclusions, the context is sufficient for an agent to choose it over other event-sending tools.

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