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

"Read-only" merely restates the annotations (readOnlyHint=true, destructiveHint=false, idempotentHint=true). With annotations already covering the safety profile, the description adds nothing new — no note about error behavior for unknown account IDs, no mention of the openWorldHint implication that data may change.

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 short fragments, front-loaded with the resource; nothing is padded. The brevity is appropriate in form even though the content is thin.

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?

No output schema, a required UUID parameter, and a nested free-form `extra` object with no explanation. The description is far too thin to bridge those gaps for an agent.

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 bears the full burden, yet it says nothing about account_id (format, where to obtain it) or the nested `extra` object, which is completely undocumented in both schema and description.

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 names the resource (one connected account) and the aspect being fetched (status), but "status" is vague — it doesn't say what a status contains or how it differs from siblings like get_account_health or get_account_limits. An agent can guess the general area but not the precise purpose.

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?

No when-to-use guidance, no prerequisites, no alternatives. It doesn't say whether it should be called before or after other account tools, or which situations call for it versus get_account_health.

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