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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered elsewhere. The description adds that the result is scoped to the authenticated caller and that the identity is "stable" (useful for caching/ID reuse), but says nothing about auth failure behavior or whether the value can change over time.

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 front-loaded sentence with zero filler — the subject (authenticated account identity) arrives immediately. There is nothing that could be trimmed without losing meaning.

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-argument read tool with full annotation coverage and an output schema that documents the returned fields, the description supplies what the agent needs: scope (this caller) and nature of the payload (identity). Only the auth-prerequisite is left implicit.

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 meaning for the description to supply; the baseline for a parameterless schema applies. Nothing is missing in this dimension.

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?

"Return the stable identity of this authenticated Average Rent account" gives a specific verb (return) and a specific resource (the caller's account identity). It is clearly separable from siblings like get_account_usage or get_rent_history, though it never names an alternative explicitly.

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?

Usage is only implied: "this authenticated ... account" plus the zero-parameter schema makes applicability self-evident (no arguments to choose, so it always targets the caller). There is no explicit statement of when to prefer it over get_account_usage or any exclusion.

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