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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds real value beyond that: the required `profile:read` scope and, importantly, the warning that user-authored text arrives in `untrusted_fields` and must be treated as data, never instructions — a genuine security-relevant behavior not expressed in any structured field.

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, front-loaded with purpose and scope requirement, then the one non-obvious return-value warning. There is no filler, and the injection-defense note is placed last where it is most likely to be retained before the call.

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, the description must carry the return-value burden, and it does flag the `untrusted_fields` structure and its handling rule. It omits what other fields the profile returns and whether the payload is nested, which leaves a modest gap for an agent deciding how to consume the result.

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 per the rubric this is the baseline case; the schema fully closes the surface with additionalProperties=false. The description correctly avoids restating parameter details and instead spends its words on response semantics.

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 pairs a clear verb with its resource ('Get my profile') and adds the 'my' scope, so it is not a pure restatement of the name. However, it gives no differentiation from the closely related siblings in this server, notably get_me, get_account, and get_account_billing, so an agent cannot tell from the description which of these returns the profile record.

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 statement of when to choose this tool over get_me or get_account, and no when-not guidance. The only usable condition is the implicit prerequisite of the `profile:read` scope, which is auth information rather than selection guidance.

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