Get GTM record

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false, and destructiveHint=false. The description adds useful context by noting only active relationships are returned, but it does not clarify behavior when both ID and key are provided, when neither is provided, or what errors may occur.

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 front-loaded sentence with no filler or redundancy. It communicates the essential operation and scope efficiently.

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 no output schema and three parameters with none required, the description omits important operational details such as the mandatory id/key relationship, how recordType factors into lookup, and expected return behavior. The sibling tool list further highlights the need for clearer selection guidance.

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. It explains that lookup can happen by ID or key, but it does not define what 'key' means, explain when recordType is needed, or clarify that at least one identifier is required despite no required parameters.

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 clearly identifies the verb ('Get'), the resource ('one governed record'), and the retrieval mechanism ('by ID or key with active relationships'). This distinguishes it from sibling search/context/lineage tools, which target different resources or return collections.

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?

It implicitly indicates use when you have a specific ID or key and need a single governed record. However, it does not explicitly say when not to use it or name alternative tools like search_catalog or get_data_definition, leaving routing decisions to inference.

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