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

With no annotations, the description carries the full burden. It implies a read-only listing operation and explains where connections come from, but it omits permissions, pagination/ordering, whether revoked connections are included, and any return-shape details.

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 compact sentences with no wasted wording. The purpose is front-loaded, and the downstream use of _id is added immediately after.

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 simple one-parameter list tool, the description covers what is listed, the workspace scope, and how returned IDs are used. The remaining gaps are modest: no return fields beyond _id, no pagination/order, and no auth context.

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. 'In this workspace' gives semantic meaning to workspaceId as the scoping parameter, but it does not explain the expected ID format or where to obtain a workspace ID.

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 specific verb and resource ('List the OAuth connections') and scopes it to a workspace. It also distinguishes this from the connection-creation path by naming console creation and get_connection_url links.

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 clear usage context: use this to find existing connections and take a connection's _id for a block's connectionId. It does not explicitly say when not to use it or directly frame get_connection_url as the alternative for creating connections.

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