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 still adds real value beyond the structured fields: the required `account:read` scope and the security-relevant note that user-authored text appears in `untrusted_fields` and must be treated as data, never instructions.

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 sentences with no filler, and the safety-relevant `untrusted_fields` warning is stated up front rather than buried. The opening sentence, however, merely echoes the title and could have carried differentiating information instead.

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 is the only place an agent can learn what the account payload contains, and it only hints at one field (`untrusted_fields`). It omits the shape of the account object and how it relates to sibling getters, leaving a meaningful gap for a no-arg read tool.

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 takes zero parameters, and the schema is correspondingly empty, so there is nothing for the description to disambiguate. The baseline of 4 applies; no parameter meaning is missing or misstated.

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?

"Get my account" states a verb and resource, but it is essentially a restatement of the title and does not distinguish this tool from siblings like get_me, get_profile, or get_account_billing. An agent cannot tell from the description alone which of the account-related getters returns what.

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?

There is no guidance on when to use this tool versus get_me, get_profile, or get_account_billing, and no stated prerequisites beyond the `account:read` scope. The permission note is context, not usage direction.

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