Check Anypoint connection

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

With no annotations, the description carries the full burden, and it does distinguish itself as a verification/inspection read rather than a mutation and frames itself as a troubleshooting entry point. It omits whether verification fails hard on bad credentials and what the output looks like, which is a minor gap given zero parameters.

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?

Two tightly written sentences with no filler. The identity/verification purpose comes first and the troubleshooting cue is placed last as the actionable instruction.

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?

Although there is no output schema, the description enumerates the fields it surfaces (business group, host, environment allowlist), which is enough for an agent to know what it gets back. Only the failure semantics of a bad-credential check are unstated.

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 tool takes no parameters, so there is nothing to disambiguate; baseline is 4. The description correctly indicates the results are derived from server-side configuration rather than caller-supplied input.

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 pairs specific verbs (verify, show) with concrete resources (Anypoint credentials, business group, host, environment allowlist), going well beyond the name 'whoami'. It is clearly a diagnostic/identity tool, which cleanly separates it from the list_* siblings.

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 gives an explicit triggering condition: 'Use this first when a call fails.' That is real when-to-use guidance. It stops short of naming alternatives or stating when not to use it, but no sibling serves the same diagnostic purpose.

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