Configure external analytics

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

Annotations provide idempotentHint=true and destructiveHint=false. Description adds context about no API key storage and env var sourcing. Shows it's a configuration mutation (not read-only) consistently with 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?

Three sentences, no fluff. Front-loaded with primary purpose. Every sentence adds value: distinguishes from sibling, explains providers, and key security detail.

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 8 parameters, 1 required, and no output schema, description covers main aspects: purpose, sibling distinction, provider specifics, env var usage, and enable/disable. Lacks success/error details but sufficient for configuration tool.

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 63% (moderate). Description adds meaning: explains provider options (e.g., custom endpoint substitution), notes Google Analytics needs OAuth, and clarifies enabled false turns proxy off. Goes beyond schema.

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?

Description clearly states verb 'Configure', resource 'external analytics provider', and explicitly distinguishes from sibling 'set_site_analytics' which injects tracking. It specifies that this tool reads site traffic.

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?

Provides explicit when-to-use (reading traffic) and when-not (injecting tracking) via distinction from set_site_analytics. Also gives provider-specific guidance (e.g., Google Analytics needs OAuth) and disabling via enabled:false.

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