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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the safety profile is covered. The description adds only that scoring spans eight weighted dimensions, which the schema already enumerates, and discloses nothing further about how the score is computed or surfaced.

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 sentences, front-loaded with the core purpose. The trailing promotional URL ("See the full version at...") doesn't aid tool selection but is brief enough not to seriously harm the structure.

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?

With no output schema, the description should explain what the score result looks like (numeric score, dimension breakdown, etc.), and it doesn't. Inputs are fully documented, so the gap is the return-value expectation for a scoring 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 coverage is 100% with each of the eight enum parameters documented, including weights, so the schema does the heavy lifting. The description adds no parameter meaning beyond what the schema provides, which is the correct baseline at full 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?

States a specific verb ("Score") and resource ("Google Tag Manager container health") and clarifies the scope as "eight weighted dimensions covering tag hygiene, consent, and reconciliation." An agent can tell what it does, though it doesn't explicitly differentiate itself from sibling audit tools like tech_stack_duplication_inspector.

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 offers no when-to-use guidance, no prerequisites, and no alternatives to compare against. It explains what the tool does but not when an agent should reach for it versus another auditing sibling.

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