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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavioral context beyond them — that it takes and stores no credentials and that authentication happens out-of-band in the portal — which is meaningful for an agent reasoning about a connect flow.

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, front-loaded with the return value and the connection options, then the security constraint, then the usage conditions. No filler and every sentence carries distinct information.

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?

For a zero-parameter, non-destructive read with no output schema, the description covers purpose, return value, security expectations, and triggers. Minor gap: it does not clarify how this relates to its closest sibling use_demo_environment, which also concerns sample-data connections.

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?

Zero parameters, so there is nothing to disambiguate; the description correctly reinforces this by stating the tool takes no credentials. The baseline for no-param tools applies and no parameter detail is missing.

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?

States a specific verb+resource ('connect an EPM environment') and what the tool actually returns ('the link to the connect portal'), plus the three connection paths it describes. An agent can distinguish it from list_connections or use_demo_environment because the description positions it as the zero-input guidance/portal-link tool.

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 names the three triggering conditions: no connection yet, wanting another one, or fixing a failing one. It also pre-empts the wrong expectation by saying credentials are entered in the portal, not here, which routes the agent away from trying to collect secrets.

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