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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered by structured data. The description adds one useful behavioral fact — that the lookup is implicitly scoped to the authenticated account rather than an arbitrary target — but says nothing about what is returned or whether the call can fail when no account is authenticated.

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?

A single eleven-word sentence with zero filler and the subject (authenticated user's data) front-loaded. It is appropriately sized, though it is arguably too terse to be maximally useful given the absence of an output schema.

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 could learn what comes back, and it stops at the vague phrase 'profile and business information'. It is otherwise adequate for a zero-parameter read whose annotations already cover the safety profile.

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, so there is no parameter semantics burden to carry; the baseline for a no-param tool is 4. The description correctly implies no input is needed by framing the call around 'the authenticated user'.

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?

Names a specific verb (get) and resource (account info), scoped to the 'authenticated user' so the agent knows it is not a target-selectable lookup. It does not, however, distinguish itself from near-neighbours like get_customer_profile, get_brand_identity, or get_connected_platforms, which overlap with 'profile and business information'.

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 when-to-use guidance at all: no indication of when this should be preferred over get_customer_profile, get_brand_identity, or get_billing_status, and no prerequisites mentioned. The agent must infer usage purely from the name.

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