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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered without the description. The description adds nothing about auth requirements, side effects, or limits beyond what the annotations state; its field list is closer to return-value documentation than behavioral disclosure.

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 sentences, zero filler, and the identity of the resource is front-loaded before the routing note. 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?

With no output schema present, the enumerated field list is exactly the return-value information an agent needs to decide whether this tool satisfies the request. A parameterless, annotation-covered identity read needs nothing more.

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 baseline is 4. There is no parameter syntax, format, or validation left for the description to compensate for.

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?

States a specific resource ('the authenticated Signed user's own profile') and enumerates the returned fields (name, login, email, plan, home currency, investing preferences). The phrase 'authenticated ... own profile' cleanly separates it from the sibling get_user/get_person lookups, and the closing sentence draws the boundary against get_portfolio.

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?

It explicitly routes the agent away from this tool when aggregate portfolio metrics are wanted ('live on get_portfolio'), which is a genuine alternative-handling signal. It stops short of stating the positive trigger (e.g. 'call this when you need the current caller's identity') or any exclusion involving get_user.

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