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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is covered. The description adds the useful fact that the result reveals whether trading is switched off, but says nothing about freshness, caching, or permissions. With annotations carrying the safety burden, this is adequate but not rich.

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?

One dense sentence covering contents followed by a usage cue and a literal call example — front-loaded with zero filler. The example string is a small but genuine convenience for an agent constructing the call.

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?

An output schema exists, so return values need not be described, and the description covers scope plus when to invoke. Nothing critical is missing for a zero-required-parameter read tool, though it could note what to do when the workspace data looks stale or restricted.

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 100%, and the single response_format parameter is fully documented in the schema including its default and the concise/detailed distinction, so the baseline of 3 applies. The description adds nothing about the parameter, though "Example: {}" hints that no arguments are required.

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 resource (this connection's workspace) and enumerates what it surfaces: plan, plan limits/features, and whether trading is disabled. This is clearly distinct from the account/order siblings, though it does not explicitly contrast itself with possibly-overlapping tools like get_usage or get_account_status.

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?

"Call it first when unsure what the user can do" gives a concrete trigger and a priority ordering, which is real guidance. It stops short of naming alternatives or when-not-to-use conditions, but the context is clear.

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