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

Annotations already cover the read-only, idempotent, non-destructive, closed-world profile, so the bar is lower. The description still adds two things beyond them: the required `account:read` scope and an explicit safety directive that human-authored text appears in `untrusted_fields` and must be treated as data, not instructions — a meaningful behavioral disclosure for a tool returning user-supplied content.

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 with no padding, and the security note is well placed. However, the opening fragment "Get me." carries no information and the phrase "Text people wrote is listed in untrusted_fields" references an output field that has no documented shape, which is slightly opaque.

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 no-parameter read, the definition covers auth scope and output safety, which is reasonably complete. It still leaves the actual return content undefined — profile, account, or user record — and there is no output schema to compensate, so key context is missing.

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 and there is nothing for the description to disambiguate. It correctly adds no redundant parameter prose.

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 first sentence, "Get me.", simply restates the tool name and title rather than stating a verb plus a concrete resource. An agent must infer that this returns the authenticated user's own identity/profile, and nothing distinguishes it from siblings like get_account, get_profile, or get_me-adjacent reads.

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 only usage-shaped information is the prerequisite "Needs `account:read`", which tells the agent what auth is required but not when to choose this over get_account or get_profile. No when-to-use or when-not-to-use condition is given.

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