environments_reauthorize

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

Describes the side effect: rotating the auth token and causing old snippets to stop working. Since no annotations are provided, the description bears full responsibility and does so adequately. It could mention irreversibility but the warning covers the main impact.

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?

Three sentences with zero waste: first sentence states purpose, second lists prerequisites, third warns of impact. The [PUBLISH] tag front-loads context. Highly concise and well-structured.

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?

Covers purpose, prerequisites, and consequences. The absence of an output schema and return value description is a minor gap, but the critical behavioral context is present. A complete description for a mutation tool with side effects.

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 descriptions for each parameter. The description reinforces the confirm parameter requirement but adds no new semantic detail beyond the schema. Baseline of 3 is appropriate.

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?

Clearly states the tool re-generates an authorization code for a GTM environment. The verb 're-generate' and resource 'authorization code' are specific, and the [PUBLISH] tag distinguishes it from other environment tools like create or delete.

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?

Explicitly mentions prerequisites (GTM_MCP_ENABLE_PUBLISH=true and confirm=true) and implies use when rotating auth tokens. However, it does not explicitly state when not to use or list alternatives, so it lacks full exclusion guidance.

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