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 a real precondition beyond the annotations ('Requires a connected account') and enumerates the returned fields, which matters since there is no output schema. It stops short of saying what happens when the account is not connected.

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, zero filler: the resource and scope come first, the returned fields second, the precondition last. Every clause earns its place.

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?

For a zero-parameter read tool with full annotation coverage, the description supplies what the structured data cannot: the identity scope, the field list (no output schema exists), and the connected-account precondition. The only real gap is the absence of an explicit pointer to get_profile for other members.

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 the schema has nothing to document and there are no parameter semantics for the description to clarify. Baseline 4 applies; no parameter-level value is added or lost.

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 with scope ('the signed-in member's own profile') and enumerates the fields it returns, which an agent can act on immediately. It distinguishes itself implicitly from the sibling get_profile via 'own', but never names that sibling explicitly, so the routing signal is weaker than it could be.

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?

The precondition 'Requires a connected account' is stated, which is genuinely useful context, but there is no explicit when-to-use guidance or a named alternative (e.g. use get_profile for another member). Usage is only implied by the word 'own'.

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