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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior, so the description adds useful context by stating the guidance is deterministic and sourced from maintained playbooks. It also explicitly clarifies that the tool does not change a website, contact a vendor, or verify a fix, which goes beyond the annotations and prevents false assumptions about side effects.

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?

The description is two sentences and front-loads the core behavior before stating limitations. Every sentence earns its place by defining both what the tool returns and what it explicitly does not do.

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, single-parameter lookup with a rich annotation set and an output schema, the description covers the essential behavior and safety boundaries. The remaining gaps are mainly the input semantics for 'tracker' and explicit sibling routing, which are less critical given the output schema and annotations.

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?

There is one required parameter, 'tracker', but schema description coverage is 0%, so the schema provides only type and pattern constraints. The description says 'tracker-specific' but does not explain expected naming format, matching behavior, case sensitivity, or what happens with an unknown tracker, leaving the parameter semantics substantially undocumented.

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, 'Returns', and a specific resource, tracker-specific consent-gating guidance from maintained playbooks. It clearly frames the tool as advisory rather than an inspection, export, or mutation tool, though it does not explicitly name or differentiate from any sibling.

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: an agent should call this when it needs remediation guidance for a known tracker. However, the description gives no explicit when-to-use guidance, no prerequisites, and no alternatives among the sibling tools such as inspect_site_tracking or interpret_consent_evidence.

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