check_environment

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

With no annotations, the description carries the full burden of behavioral disclosure. It does reveal that the secret key is not returned, which is useful security context, but it does not state whether the operation is read-only, whether 'refresh' changes behavior, or what side effects (if any) occur. This is only minimal disclosure.

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 sentence that is front-loaded with the primary action and keeps the security-relevant qualifier at the end. There is no filler or redundancy; every word contributes meaning.

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 output schema exists, return format is partially covered, but the description omits when to use the tool, the meaning of the refresh parameter, and behavioral guarantees beyond the secret key. An agent would likely need to inspect sibling tools or rely on trial-and-error to invoke it correctly.

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 loosely maps to the 'environment' parameter ('one configured Nango environment') but says nothing about the 'refresh' parameter, its default, or how it affects resolution. The parameter semantics are largely unexplained.

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 ('Resolve') and resource ('one configured Nango environment'), and adds a meaningful qualifier ('without returning its secret key') that distinguishes it from a raw list or fetch. However, 'resolve' is somewhat imprecise and could mean validate, fetch, or materialize, so it falls short of a 5.

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 gives no explicit guidance on when to use this tool versus alternatives like list_environments or get_connection. The singular phrasing implies it is for checking one specific environment, but no exclusions, prerequisites, or sibling comparisons are provided.

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