Check GTM readiness

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds the specific domains it validates, which is useful context beyond the annotations. However, it does not disclose behavior like what happens if the recordId is invalid, whether it aggregates data from other services, or how findings are reported. This is acceptable given the annotations already assure safety.

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 a single, efficient sentence that front-loads the action ('Check') and lists the specific areas. It contains no filler and gets to the point immediately. The structure is clear and easy to parse.

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 check with one parameter, the description covers the main scope of the tool. However, it does not describe the return value or output format, nor does it mention any preconditions (e.g., requiring an existing record). Since there is no output schema, the description could reasonably state that it returns a readiness assessment, but its absence leaves some ambiguity for agents expecting a structured result.

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 0%, so the description must compensate for the undocumented 'recordId' parameter. The description does not mention recordId at all, leaving agents to infer its meaning from the tool name and context. While it is a common identifier, the tool does not clarify its format, scope (e.g., GTM record vs. another entity), or required context. This is a notable gap.

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 clear verb ('Check') with a specific resource and enumerates the aspects being checked: lifecycle, verification, ownership, runbook linkage, and pending source updates. This is specific enough to convey the tool's core function, though it does not explicitly differentiate it from siblings that also relate to status or readiness, such as gtm_module_status or gtm_get_record.

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 provides no guidance on when to use this tool versus the alternative sibling tools. It does not state conditions, prerequisites, or exclusions. Given the large sibling set, an agent receives no help in choosing this over gtm_module_status or gtm_get_record for a similar readiness inquiry.

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