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

Annotations already declare readOnly, non-destructive, closed-world. The description adds real context beyond them: results are returned 'in plain words', the success condition is defined ('turns green when all three have arrived'), and it notes the operation is 'Free'. It omits auth needs and rate limits.

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?

Short and front-loaded with the purpose in the first clause, followed by the success semantics and cost note. Sentence fragments ('Free.') are terse but readable; nothing is wasted.

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 read-only tool this covers the purpose and the pass condition, and no output schema exists to explain. However it leaves the sole parameter undocumented and gives no sense of the response shape beyond 'plain words', so it is adequate rather than complete.

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?

The single siteId parameter has 0% schema description coverage, and the description never mentions it. The description does not compensate for the coverage gap, leaving the only parameter's meaning and expected format unexplained.

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 states a specific check: whether the live site is sending events, crawler hits, and goals, plus what is missing. That is distinguishable from tracking_install (which sets up rather than verifies), though no sibling is named explicitly.

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?

Usage is implied rather than stated: an agent can infer this is the tool to call to verify tracking status. There is no explicit when-to-use, when-not, or routing to tracking_install or funnel_check for related workflows.

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