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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false, and destructiveHint=false. The description adds substantial behavioral context beyond that: scoping to the user's own and shared connections, the environment override precedence, the fact that hosted applications reflect the last test, and multi-connection naming expectations. There is no contradiction with annotations.

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 front-loaded with 'Lists the Oracle EPM connections' and then efficiently covers return fields and usage guidance. Despite being dense, every sentence adds useful information for selecting and interpreting the tool.

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?

With no output schema, the description appropriately explains the important return fields (id, label, environment, default application, hosted applications, auth type, status, default flag). For a zero-parameter, read-only listing tool with annotations already covering safety, this is complete enough to call 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?

The tool has zero parameters, so there is no parameter semantics to document and the baseline score is 4. The description does not need to compensate for missing parameter coverage.

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 gives a precise verb and resource: it lists Oracle EPM connections, states the scope (the user's own plus tenant-shared ones), and enumerates the returned fields. An agent can distinguish this listing tool from siblings like connect_epm_environment without opening any schema.

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 explicitly says to use this tool to choose the connection argument for other tools or to verify that a connection exists before calling Oracle. It also gives multi-connection guidance about naming the connection in every call. It does not name explicit alternatives or when-not-to-use conditions, so it stops short of a 5.

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