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 adds meaningful context beyond that: the data is always the caller's own identity with no target parameter, and it includes the connection's permission scope, which is behaviorally relevant for deciding whether other mutations are permitted.

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 sentence, front-loaded with the subject (the signed-in person), listing exactly what comes back. No filler, no restatement of the title, nothing to trim.

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?

There is no output schema, so the description must convey return contents, and it does list the main fields. The phrase 'what this connection is allowed to do' is vague about whether this is a scope list, booleans, or role names, and the list may not be exhaustive, leaving a small gap for a zero-parameter read.

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 no parameter semantics are needed and the baseline is 4 by default. The field list in the description concerns return values, not inputs, and is complementary rather than redundant.

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 a specific resource (the signed-in person's profile) and enumerates the fields returned: name, language, time zone, weekly posting goal, and connection permissions. This is clearly distinct from siblings like get_plan_usage or list_connected_accounts, though the verb is only implied by the tool name rather than stated outright.

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 explicit when-to-use guidance and no named alternative or exclusion. Usage is strongly implied by the self-scoped, zero-parameter nature of the tool, but an agent gets no statement like 'call this first to resolve the current account' or 'do not use this to inspect other accounts.'

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