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

The description claims that 'Mutations require preview and confirmation,' which directly contradicts the annotation stating 'readOnlyHint: true.' This inconsistency is severe, as it misrepresents the operational nature of the tool to the agent.

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 definition is highly concise. It uses two sentences to state the purpose, the operational environment (Nexscope), and the safety requirement. It is front-loaded with the core function.

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 the single parameter and the presence of safety annotations, the description provides sufficient context regarding system usage and credential management. The primary issue detracting from a 5 is the internal contradiction regarding the operation's safety profile.

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?

The schema coverage is 100%, meaning the input parameter (`connectionId`) is fully described in the structured data. The description adds only mild context about using the Nexscope connection rather than critical semantic meaning beyond what is already defined in the schema.

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 title and description clearly state the tool's purpose: refreshing Amazon Ads tokens. While the description is clear, it could benefit from explicitly stating that this is for expired or expiring access tokens to fully distinguish it from general API calls within the Amazon Ads group.

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 context that the connection is managed by Nexscope and includes a warning about mutation safety, which guides high-stakes usage. However, it does not explicitly define the conditions under which a token refresh should occur (e.g., upon receiving a 401 error).

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