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

Annotations already declare readOnlyHint=true, so the safe-read profile is covered. The description adds that the caller must be authenticated and supplies value-format conventions (6-character case-sensitive IDs, UTC ISO 8601 timestamps, meters, seconds), but several of these (distances, durations) are not fields this tool returns, suggesting generic boilerplate.

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?

The purpose is correctly front-loaded in the first sentence. However, the trailing format conventions are generic and partly irrelevant to the four fields actually returned, so not every sentence 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, the description carries the burden of describing the return value, and it does so by listing the four profile fields. The only gap is the absence of guidance about when this tool is preferable to person_read.

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 has zero parameters and the description explicitly confirms 'Takes no arguments', matching the empty schema with additionalProperties:false. Baseline 4 applies for a no-parameter tool.

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 states a specific resource and scope: the authenticated caller's own profile, with the returned fields enumerated (id, email, name, language). This implicitly distinguishes it from the sibling person_read, since it is scoped to the caller rather than an arbitrary person, though the sibling is never named.

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 when-to-use guidance and no reference to alternatives such as person_read. 'Takes no arguments' is a usage fact but not a routing rule, so an agent gets no help deciding between this and the other read tools.

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