Add analytics property host

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

Annotations already declare mutation, idempotent, non-destructive, closed-world. Description adds valuable behavioral context: changes live tracking on the user's site, keeps canonical host/site key, and does not use credits. Does not contradict 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?

Front-loaded with verb, resource, and endpoint; each short sentence adds distinct information (targeting, side effects, cost) with no waste.

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 2-param mutation with rich annotations and no output schema, the description covers what it does, how it targets, its live-tracking impact, and cost. Missing explicit alternatives and permission details, but adequate overall.

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?

With 0% schema description coverage, description must compensate. It clarifies propertyId is the sole target and hostname is a public collection hostname, but does not explain format or constraints beyond what the schema provides (pattern, integer minimum).

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?

States a specific verb 'Add' and resource 'public collection hostname' with endpoint PATCH /api/v1/analytics/property. Distinguishes from generic property creation by scoping to hostname addition and targeting propertyId alone.

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?

Gives context such as 'target by propertyId alone' and 'keeps the canonical host and site key', but does not explicitly state when to use this versus siblings like analytics_create_property or analytics_verify_property, nor 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.